Renovation as a product, live in three markets in 8 months
Welcome Renovation wanted to sell luxury remodeling with clear scope, fixed pricing and predictable delivery. We built the homeowner app, the field app and the admin system behind that promise, and it launched across Southern California with 15,000 active users.
Fixed prices don't survive a group chat
Residential remodeling has run the same way for decades: personal calls, group chats, photos on someone's phone and spreadsheets. The result is familiar to every homeowner. Pricing is opaque, schedules slip and nobody is quite sure what has been paid for.
Welcome Renovation's business model depended on the opposite: clear scope, fixed pricing and predictable delivery for the California luxury market. That promise needed one record of every project that the homeowner, the site manager and the office could all see and trust.
The brief: software that lets Welcome Renovation operate as a tech-enabled product company instead of a traditional general contractor, across three regions from day one.
Payment friction erodes trust
Manual invoicing and unclear links between money and work create disputes. Funds had to release only when physical work was verified, in a way both sides could check.
Late change orders are the costliest
“This isn't what I imagined” at the punch-list stage costs far more than the same conversation during discovery.
Every city has its own paperwork
Municipal codes, permits and contract structures differ across LA, Orange County and San Diego. Homeowners should never have to know that.
Four decisions that made the promise enforceable
Release money only on verified work
Each project is split into milestones with set amounts. When the manager submits photos, video and sign-off, the milestone closes and Stripe releases the payment. Both sides see what was verified, what was paid and what is pending, with an audit-grade record of who verified what and when.
Two native apps for two very different users
Homeowners need visibility and answers without asking anyone. Managers need daily reports, video walkthroughs and punch lists from job sites with poor connections. Both apps are native Swift and Kotlin because high-resolution media and background sync hit cross-platform limits. The duplicated codebase cost was worth it for this workload.
Settle taste before the build starts
A multi-step design intake maps each homeowner's preferences to the curated collections the business sells, such as Santa Barbara and Bel Air. It aligns expectations during discovery, where a change costs far less than at the punch-list stage.
Keep regional rules out of the interface
Contracts, design briefs and municipal permits are signed in the app through DocuSign. Regional differences live in the document and workflow layer, so one product could launch in three markets at once. Stripe, DocuSign and Pipedrive were integrated rather than rebuilt, which kept engagement time on what differentiates the business.
Weeks 1–4 · Discovery and UX strategy
User journeys, data model, integration scope.
Months 2–3 · Core infrastructure
NestJS backend, Stripe, DocuSign and Pipedrive.
Months 4–6 · Native mobile
Homeowner and manager apps, media pipelines.
Month 7 · Integration testing and QA
Financial flows and cross-device checks.
Month 8 · Regional launch
LA, Orange County and San Diego.
A platform that keeps adding services
The platform launched in three Southern California markets at once with 15,000 active users, and every milestone payment is tied to verified completion that homeowner and manager can see in real time. MetaProject continues to support and evolve it.
Next on the roadmap: schedule optimisation from historical project data, new modules such as HR and payroll on the same infrastructure, and long-term space management for homeowners after the renovation ends.
15,000
active users at launch
3
regions launched simultaneously
8 months
from discovery to deployment
4
native builds: two apps on iOS and Android
15,000
active users on the platform at launch
3
apps shipped: homeowner, field and admin
8 months
from discovery to multi-region deployment
3 regions
launched simultaneously in Southern California
Native homeowner and project-manager apps for iOS and Android, a web admin dashboard, milestone payments, a DocuSign document suite, design preference intake and Pipedrive CRM integration.
Swift · Kotlin · Node.js / NestJS · Next.js + TypeScript · Stripe · DocuSign · Pipedrive · AWS S3 + CloudFront · automated CI/CD · BrowserStack
Questions about this project
Why native mobile rather than cross-platform for this engagement?
The decision was driven by the media workload. The field app uploads high-resolution photos and video from variable-quality on-site connections, and the homeowner app delivers that media back at full fidelity. Cross-platform frameworks (React Native, Flutter) handle standard form-based and content-driven apps well, but hit a performance ceiling with media-heavy workflows and reliable background sync. Native Swift and Kotlin let us hit that performance bar without trade-offs. The duplicated codebase cost is real, but for this product class it was the right call.
How does milestone-linked payment via Stripe actually work?
The architectural pattern is "payment release on verified completion." Each project is broken into milestones with associated payment amounts. When the project manager submits verification (photos, video, sign-off) for a completed milestone, the system marks it complete and triggers Stripe to release the associated funds. Both sides have real-time visibility into what's been verified, what's been paid, and what's pending. The engineering complexity lies in defining what constitutes "verified completion" in a way both parties can trust, and providing an audit trail that supports that trust over time.
Why integrate Pipedrive, DocuSign, and Stripe rather than building these capabilities in-house?
Because each of these systems does its specific job extremely well, and rebuilding them in-house would have consumed engagement time without producing differentiation. The right architectural decision was a clear integration boundary with each: treat them as managed services for the parts of the workflow they handle best, and build the platform's actual differentiation around them. Stripe handles payments, DocuSign handles legally-binding signatures, Pipedrive handles CRM. The platform handles the orchestration.
How do you handle regional regulatory variation in a multi-region launch?
By isolating the variation in the document and workflow layer rather than letting it propagate through the user interface. Across LA, Orange County, and San Diego, municipal codes and permit structures vary, but the homeowner shouldn't have to know that. The compliance layer absorbs the variation; the surface stays clean. This pattern generalises to any multi-region product where local regulation differs but the user experience should not.
Can the platform expand to other field-service categories beyond renovation?
Yes, that's part of the current roadmap. The underlying pattern (dual mobile apps + admin coordination + milestone-linked financial workflows + integrated CRM and compliance) generalises to any field-service business that wants to move from bespoke service delivery to a productized experience. HR and payroll modules are the next planned extensions.
See more cases
Could your service business run as a product?
Tell us what you are building. We will come back with an honest view of how we would approach it.