→ Engagement spotlight / Embedded delivery
The platform went live on the promised date. Customers onboarded $400M on day one
Nine months of the build had already gone when MISSION+ arrived, and the launch date was a market window rather than a project milestone, so it could not move without the proposition moving with it.
Roughly $900K of build and delivery cost was avoided against the original plan, which is a comparison against a plan rather than a measured spend.
→ The sequence / how the engagement ran
Four decisions, in this order.
01
Work to the date the market set
The squad joined the client's existing sprint cadence and worked to client product goals rather than a separate scope document.
02
Put design inside the squad
Design sat in the same unit as engineering, so interface decisions were made against what the platform could do that sprint.
03
Flex the shape through the crunch
The squad grew for the pre-launch period and shrank after it. Reconfiguring mid-engagement is the model working.
04
Ship, then step back
The squad scaled down after launch. That was written into the plan at the start.
Team shape across the engagement / blue marks the pre-launch peak
↻ Flex A fixed-size contract cannot do this, and a large part of why the cost landed where it did is that the client was not paying for peak capacity in the quiet weeks.
→ The situation
The client knew what it was building and could not get it built in time.
The client was building a deposits platform to put global bond investments within reach of ordinary savers in Singapore. The fund management expertise was already in the building.
Nine months had gone before MISSION+ was brought in, and the launch date was not a project milestone. It was a market window, which meant it could not move without the proposition moving with it.
The team had capability gaps it could not hire into on that timeline. Singapore's market for senior product engineers was being fought over, and even a hiring process that works takes a quarter to run.
Adding contractors in a distant timezone had been considered and rejected, correctly. What was slowing the work down was the round trip on every decision, and adding people further away would have lengthened that round trip.
The question every sprint had to answer
What is the smallest version of this that a customer can put money into?
→ What was measured
The numbers, and where they came from.
Deposits on day one
Onboarded on the day the platform went live. This is a number about the product, and the engineering is the reason there was a day one.
Cost avoided
Build and delivery cost against the original plan. It compares delivery to a plan rather than to a measured alternative spend, so read it as an order of magnitude.
Slip recovered
The launch date had already slipped by nine months before the engagement began. It was met.
The squad and the design team joined the client's own sprints. A vendor workstream would have added a second set of ceremonies to a project that was already losing time between them.
The delay was decision latency, so the team had to be reachable inside Singapore hours. That is why distant-timezone contractors were rejected before the engagement started.
Design handed forward as a specification is a second decision loop, and this project could not afford another one. Interface decisions were made against what the platform could actually do that sprint.
MISSION+ scaled the squad down once the platform was live, and the engagement ended there. It is the part worth checking any delivery partner on.
→ Why it matters
A launch date that cannot move changes what you need from a delivery partner.
When the date is fixed and the scope is movable, every week has to answer the same question about the smallest shippable version. Scope moved throughout the engagement while the date held, and that single decision is what protected the market window.
The team size moved with the work, scaling up through the pre-launch crunch and back down afterwards. The client's own team took the platform forward from launch, and the squad wound down on the schedule agreed at the start.