Scaling a PropTech Startup from 3 to 15 Engineers
Architecture pattern — built as a reference implementation, not in production with paying users. The featured production case study is wintura.ai (see /case-studies/wintura-ai). This pattern documents the PropTech Iteration Sprint playbook a Soatech engagement would follow for that domain.
Architect-led, AI-accelerated. 2× faster than hand-coded shops.
Hand-coded teams, hourly billing, scope creep. Multi-month ramps before the first production-grade PR.
A Veteran Architect leads the Pod. AI tooling captured as reviewed throughput, not someone else's margin. Fixed sprint price.
Key Results
The Challenge
This reference implementation documents the Iteration Sprint pattern for scaling a property management SaaS engineering team. The scenario: a London-based platform with 500+ landlord customers and 8,000+ rental units, with a 3-person engineering team that can't keep up with demand:
- Tenant portal was the #1 requested feature — tenants needed to pay rent, submit maintenance requests, and view documents online
- Maintenance workflows were manual — property managers coordinated repairs via email and phone
- Infrastructure costs were ballooning — their AWS bill had doubled in 6 months without corresponding traffic growth
- Technical debt from early-stage shortcuts was slowing every new feature
Hiring in London is notoriously difficult. After 2 months and 30+ interviews, zero engineers hired. Senior full-stack developers in London command GBP90,000-GBP120,000, and competition from fintech and big tech makes recruitment nearly impossible for a Series A startup.
Our Approach
Month 1: Team Assembly + Integration
The reference team structure for this pattern is 6 roles, selected for the project's tech stack and working style:
- 2 senior full-stack engineers (Next.js + Node.js)
- 1 senior DevOps engineer
- 1 mid-level frontend engineer
- 1 mid-level backend engineer
- 1 QA engineer
Integration was critical. We didn't just "hand over" engineers — we embedded them:
- Added to the company's Slack workspace, Notion, Linear, and GitHub
- 1-hour daily standup at 10:00 GMT (11:00 CET — perfect timezone overlap)
- Pair programming sessions between Soatech engineers and the existing London team
- Two-week onboarding sprint focused on understanding the codebase, domain, and customer needs
By week 3, the Soatech team was shipping code to production independently.
Months 2–3: Tenant Portal
The first major deliverable was the tenant portal:
- Rent payments — Stripe integration with automated reminders and receipt generation
- Maintenance requests — Photo upload, categorization, and real-time status tracking
- Document vault — Tenancy agreements, inspection reports, and correspondence in one place
- Mobile-responsive — 65% of tenants access the portal on mobile
The portal launched after 8 weeks. Within the first month, 72% of tenants had activated their accounts.
Months 3–5: Maintenance Automation
This was the highest-impact project — replacing a chaotic email-based workflow with an automated system:
- Smart routing — Maintenance requests automatically categorized and assigned to the right contractor based on type, location, and availability
- Contractor portal — External tradespeople could accept jobs, update status, and upload completion photos
- SLA tracking — Automatic escalation if repairs weren't acknowledged within 4 hours or completed within the agreed timeframe
- Cost tracking — Every maintenance job linked to the property with full cost history
Property managers reported saving 3–4 hours per day on maintenance coordination.
Month 5–6: Infrastructure Optimization
Our DevOps engineer audited the entire AWS infrastructure:
- Right-sized EC2 instances — Most were over-provisioned by 2–3x
- Moved to reserved instances — 40% savings on compute costs
- Implemented caching layer — Redis for frequently-accessed property and tenant data
- Database optimization — Query analysis and indexing reduced average response time from 800ms to 120ms
- CI/CD pipeline — Automated testing and deployment replaced manual processes
Monthly AWS bill: reduced from £8,200 to £4,900.
The Results
After 6 months:
- Feature releases: From 1–2 per month to 5–6 per month
- Tenant portal adoption: 72% of tenants active within 30 days of launch
- Maintenance efficiency: Property managers saved 15+ hours per week
- Infrastructure: 40% cost reduction, 85% faster average response time
- Zero turnover: All 6 Soatech engineers remained on the project for the full engagement
Engagements like this typically extend to an ongoing dedicated team model.
Why It Worked
-
Timezone alignment is underrated. Soatech operates CET — just 1 hour ahead of London. Standups, pair programming, and Slack conversations happen naturally, not at awkward hours.
-
Embedding > outsourcing. The team uses the company's tools, attends their retros, and understands their customers. This isn't body shopping -- it's a genuine team extension.
-
DevOps pays for itself. The infrastructure optimization saved £3,300/month. The DevOps engineer's monthly cost was less than that. The ROI was immediate and obvious.