The milestone cards below show where the technical platform stands, but they do not mean there is already a usable iOS and Android app. The .NET MAUI client is still a major missing workstream that keeps the overall technical score low.
How Far The Technical Build Has Moved From Foundation Toward Beta
This page translates the roadmap, backlog, and current implementation into one founder-readable technical progress view. Percentages are milestone-completion estimates based on implemented backend capabilities, architecture work, founder technical visibility, and what still blocks the first full marketplace loop.
20%
Estimated technical completion across the eight roadmap milestones.
2 / 8
Milestones are materially underway, but none of the highest-value workflow milestones are actually closed.
6
Major technical milestones still need real workflow execution, not just shell wiring and planning.
45%
Backend and API progress is ahead of the overall score, which is why the page now separates platform progress from total technical delivery.
0%
.NET MAUI iOS and Android app progress is still effectively at zero, and that materially pulls down the overall technical percentage.
Overall Build Distance
Think of this as the horizontal distance for the technical platform only, from first bootable system to limited-city beta. The current build is past raw setup and identity, but still well before the first full booking-money-operability loop and before any real mobile-client execution.
Current estimated position: 20%
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
The backend can be materially ahead while total technical delivery stays near 20%, because mobile app execution, full booking flow, payment flow, and operator tooling are still incomplete.
Milestone-by-Milestone Progress
These numbers are meant to be decision-friendly, not falsely precise. They represent how much of each technical milestone is materially implemented, not how many files exist.
75%
Bootable backend, migrations, health checks, OpenAPI, architecture docs, founder portal, and data-platform guardrails are all in place.
60%
Identity flows, role-aware authorization, account profile editing, and customer-technician home/profile endpoints exist. This is close, but client polish and some downstream readiness rules remain.
25%
Technician onboarding, admin approval or rejection, profile persistence, address capture, and compliance-record structure are present. Evidence upload and storage are still missing.
20%
Customer profile and address capture exist, but customer verification level, trust-summary visibility, and payment readiness are not finished yet.
5%
Service catalog and booking bootstrap are there, but the first true booking lifecycle has not been implemented.
0%
The ledger and payout direction is defined architecturally, but the operational payment flows are still future work.
10%
Technician verification review is the first real admin slice. Broader booking, trust, incident, and reporting tools are still open.
0%
Founder-facing communication and architecture visibility are ahead of schedule, but launch-hardening must follow real booking, payment, and operator workflows.
mostly done
active implementation zone
future milestone
Technical Delivery Tracks
The overall 20% estimate includes more than the backend. It also includes the client apps, core workflow execution, and operator-facing technical surfaces. This section makes that weighting explicit.
45%
The backend has real technical substance now: persistence, auth, roles, profiles, admin review, contracts, migrations, and technical planning are all established.
0%
No real mobile app implementation exists yet. The roadmap explicitly includes a .NET MAUI client, so this remains a major unfinished technical track.
10%
There is early booking preparation and bootstrap logic, but not the first end-to-end request, response, schedule, and shared booking-state loop.
10%
Admin technician review exists, but the wider operational surface founders need for incidents, bookings, trust, and money flow is still ahead.
What Is Already Implemented
This is the concrete technical progress already visible in the repository and backend, not aspirational planning language.
Platform and data foundations
- Modular monolith solution structure is established.
- PostgreSQL persistence, migrations, and DbContext model are working.
- Health checks, OpenAPI, and developer boot path exist.
- Option 2 data-platform strategy is documented and founder-visible.
Identity and role access
- Registration, login, current-user, confirmation, resend, forgot-password, and reset-password flows are present.
- Role-aware authorization policies exist for customer, technician, and admin.
- Shared account profile editing is in place.
Customer and technician profiles
- Customer home and profile endpoints persist readiness data.
- Technician home and onboarding profile endpoints persist supply-side setup data.
- Customer and technician addresses are now captured for future service-location use.
Trust and verification groundwork
- Admin verification queue and approve or reject actions exist.
- Technician compliance record model and disclosure policy are in place.
- Credential-view, compliance-view, and technician-card contracts now exist.
Booking preparation
- Service catalog bootstrap exists.
- Booking bootstrap exists for ready customers and approved technicians.
- Realtime, outbox, audit, telemetry, and ledger directions are documented.
Founder communication
- Founder portal is live.
- Platform architecture view is live.
- Roadmap, backlog, and data-platform planning are reflected in founder-friendly pages.
.NET MAUI mobile app status
- The roadmap targets a .NET MAUI app for iOS and Android.
- No real customer or technician mobile app flow is implemented yet.
- This is one of the biggest remaining technical workstreams, not a minor follow-up task.
What Still Moves The Percentage
The next visible jumps in technical progress will come from workflow proof, not more setup documents.
Next jump: booking core
The biggest single percentage move will happen when a customer can create a real booking and both sides can see the same lifecycle state.
Availability and schedule rules
Booking requests become trustworthy only once technician availability windows are enforced against the API.
Verification evidence
Technician approval needs actual document upload, storage, and operator review evidence behind it.
Customer trust summary
Technicians need a safe, role-appropriate customer trust summary before accepting real work.
Money flow
The marketplace stops being a technical prototype and starts being an operational business once payment and payout records are tied to bookings.
.NET MAUI client implementation
The technical percentage cannot move far without real iOS and Android app shells, auth state, navigation, and booking-facing screens built in .NET MAUI.
Operator tools
Founders need booking investigation, trust review, and financial-status views before limited-city beta can be trusted operationally.
This page should be treated as a founder technical view, not an engineering burndown chart. The percentages are intentionally coarse and should move only when the technical proof surface actually changes.