RealEZ Notes

Who do we actually need

Team

The founder is now part-time in both scenarios — not driving vision, roadmap, or architecture day to day, for now. That has to land somewhere real, not just get quietly dropped, which is why the Technical Product Manager role below is a week-1 hire with a bigger scope than a delivery-tracking PM, not the month-2 addition it used to be.

What changed and why it matters: with the founder stepping back to part-time, three things that used to have an owner need one again. Architecture mostly already sits with the tech lead (co-owned with the founder before) — that becomes closer to full ownership, with the founder available for occasional sign-off, not daily direction. Team coordination splits across existing roles: HR/Admin for the administrative side, the tech lead for technical direction and review. Vision and roadmap don't have a natural home in the existing roster — that's what the Technical Product Manager now owns, which is why it can't wait until month 2 anymore.

Already on the team

Hiring plan — tiered, same in both scenarios

Tier 1 · Week 1

Tier 2 · Weeks 2–4

7 hired, headroom left fully open

4 new FTE hires (tech lead, Technical Product Manager, QA, HR/Admin), plus the 2 existing engineers, plus 1 project-based designer — 7 people total against a confirmed 8–10 budget headroom. That headroom stays unspent on purpose: neither DevOps/Platform nor a second mobile engineer earned a seat on their own merits, so the room goes unused rather than filled to hit a number. If a real need shows up — a second backend engineer for Full Pilot's 2–3-state jurisdiction workload, a security engineer once there's production traffic to justify it, or a second mobile engineer if native apps for all 5 portals slip — the room is there.

What's not hired, and why

Why not Product Manager or Engineering Manager instead?

Worth stating directly, since the role changed shape this round. Product Manager alone undersells it — this person also runs delivery and owns the cross-team dependency tracking, not just prioritization. Engineering Manager doesn't fit at all: there's no people-management or hiring scope here, and a dedicated EM layer isn't justified for a 4-person engineering function anyway. Technical Product Manager is the accurate title: product ownership (vision, roadmap, prioritization) plus delivery coordination, with enough technical fluency in the two pillars to make real trade-off calls rather than just track a board.

How this compares across scenarios

Full PilotLean Pilot
FounderPart-time in both, for now — no longer a scenario difference
Tech leadSenior Backend Engineer #2, in both — owns architecture and DevOps/foundations, no dedicated hire
Vision / roadmapTechnical Product Manager, in both — week-1 hire
Mobile1 Flutter engineer covering all 5 portals, in both (flagged risk)
Designer1 project-based UI/UX designer, not FTE, in both
QA startMonth 1, with foundations — same in both
Compliance ownershipOther cofounders, in both — not a build-team hire
GTM ownershipOther cofounders, in both
New FTE hires4 (tech lead, Technical Product Manager, QA, HR/Admin) + 1 project-based Designer