The challenge
Bricklane is a property-tech agency with a flagship client whose roadmap had outpaced their internal team. They needed two more senior engineers, but hiring would take four to six months, and ramping them through their (complex, multi-tenant, white-labelled) platform would take another six. They had nine months until the client expected the next major release. The math didn't work.
Three constraints shaped the engagement:
- Senior, not junior. Bricklane's platform was complex enough that senior engineers were table-stakes; juniors would have been a net cost.
- Embedded, not arms-length. The work happened across daily standups, shared Slack, shared GitHub, shared Linear. The engineers had to feel like Bricklane engineers, not visiting consultants.
- Knowledge has to stay. Whatever the pod built, Bricklane had to be able to maintain after the engagement ended. No black boxes.
How we approached it
Three days from intro call to pod proposal. We matched a tech lead and one senior engineer to Bricklane's stack and conventions. Bricklane interviewed both engineers before accepting, a step we now do for every dedicated-team engagement. It made the engineers feel chosen rather than assigned, and Bricklane felt ownership from day one.
One-week ramp covered the codebase, deployment process, sprint rituals, and the client's domain. The pod joined sprint 1 of the next quarter. We added a third engineer in month four when scope expanded.
What we shipped
Across 9 months and 4 major releases:
Release 1, New tenant portal (months 1–7, overlapping) A complete rebuild of the customer-facing portal: tenant onboarding, document management, communication hub, payment management. ~28 weeks of pod-time, shipped on the planned date with 12 user-facing features.
Release 2, Document automation pipeline (months 3–6, overlapping) LLM-powered document classification, extraction, and routing. Reduced one specific operational workflow from ~45 minutes to under 5 minutes per case. Trained Bricklane's ops team on the prompt-management workflow.
Release 3, White-label deployment system (months 5–7) Multi-tenant deployment infrastructure that lets Bricklane's other agency clients use the same platform with branded experiences. Standalone product line for Bricklane's commercial team.
Release 4, Reporting service rebuild (months 7–8) Replaced a legacy reporting service that had become the bottleneck for monthly close. New service was 4× faster and integrated with the new portal.
Plus continuous: feature work, bug fixes, code review, and on-call rotation alongside Bricklane's internal team.
Outcomes
- 4 major releases shipped on schedule, all 4 within budget.
- Sprint commitment hit rate: 100% across 9 months, no spillover, no scope creep into the next sprint.
- Pod scaled 2 → 3 engineers in month 4 as the third release's scope was finalized.
- Bricklane retained 100% of the work. Knowledge stayed with them via documentation, weekly knowledge-transfer sessions, and Bricklane engineers reviewing every PR.
- Engagement extended +6 months. Planning a second pod for a different Bricklane client account.
- Two of the three pod engineers requested by name by Bricklane for the extension.
What we'd repeat
The interview-and-accept step before pod start mattered more than we initially thought. It made the engineers feel chosen rather than assigned, and Bricklane felt ownership from day one. Pods that skip this step start at "tolerated", pods that do it start at "welcomed."
The other lesson: scale the pod to the work, not the contract. Starting at two engineers and scaling to three when scope demanded it was much better than over-staffing from day one. Bricklane paid for the capacity they used; we ramped the third engineer at exactly the moment the third release was approved.
The third lesson, counter-intuitive but consistent across our retainer engagements, knowledge transfer doesn't happen at the end. It happens every day. Weekly knowledge-transfer sessions, code review by Bricklane engineers from week one, documentation as a Definition of Done item. By month nine, Bricklane could maintain everything we'd shipped without us. That's the goal.