RealEZ Notes

RealEZ · Founder Planning

Phase 1 Planning Notes

A growing collection of build-planning notes for RealEZ's Phase 1: two scenarios (scope, team, timeline, cost), a deep look at who we actually need to hire, job descriptions ready to post, and tech-stack reasoning. Both scenarios build with the same disciplined defaults — QA from month 1, foundations required in week 1 — as standard practice, not an option. This is a living reference — expect more pages over time.

Two scenarios, side by side

ScenarioShape
Full Pilot 6 months · 2–3 states · in-house ESIGN e-signature · direct earnest-money custody View →
Lean Pilot 5 months · 1 state · 3rd-party e-signature · no custody View →

Same team, same foundations-first discipline, same native mobile apps for all 5 portals in both — the real choice is product/legal scope and timeline, not process. See Scope for the full breakdown.

Every page

Scenarios
Full Pilot / Lean Pilot comparison, tabbed — objective, team, timeline, exit criteria, risks for each.
Scope
One matrix: e-signature, custody, geography, product focus, mobile, team size — across both.
Timeline
Gantt chart per scenario — what happens month by month.
Dependencies
What engineering is blocked on from other cofounders, and the internal build dependencies.
Team
Who we actually need, in what order, and why — the deep hiring analysis.
JDs
One job description per open role, ready to post — Husig's own careers format.
Tech Stack
Language and framework pros/cons, and how AI-native + HITL building actually works day to day.
Multi-Tenancy
Tenant data isolation and white-label — what's in the first 6 months and what isn't.
Cost
Nepal-based senior team costs, per scenario — payroll, overhead, hardware, office.
Knowledge.md
Every page above, as one long reference document.