Discovery Sprint
A clickable prototype within 48 hours, then the architecture, the stack decision and a build estimate you can take to your board.
See the Discovery Sprint →
← All engagements
Engagement 01
Discovery Sprint
Two weeks to find out what to build, how to build it and what it will cost, before you commit to a build. Within 48 hours of the first meeting you get a clickable prototype.
Start your Discovery SprintWhat you get
- A clickable prototype within 48 hours of the first meeting
- The architecture for your product
- The stack decision, with the reasons behind it
- A build estimate you can take to your board
The terms
- If you don't see value in what it delivers, you don't pay.
- If you sign a build or retainer within 30 days, the full fee comes off it.
- Your tech lead runs it from the first call.
For: Founders who need a clear plan and a real number before they commit to a build.
Other two-week sprints
Same format, a narrower question.
Board-Up Sprint
We bring up firmware on your board: drivers, connectivity and OTA running on your hardware, plus a written list of what's left before the pilot.
Start a Board-Up Sprint →Maps-Cost Audit
We trace your Mapbox or Google Maps bill back to the calls, refresh rates and device data that drive it, and hand you a prioritized plan to cut it.
Start a Maps-Cost Audit →CRA-Readiness Sprint
For products sold in the EU: an SBOM from your build, a secure-boot and update review, and a gap list against the Cyber Resilience Act.
Start a CRA-Readiness Sprint →Other engagements
02
Build
Your tech lead plus the engineers your stack needs, in two-week sprints with a weekly update.
See it →03
Tech lead and fractional CTO
Prefer to keep the work in-house? A tech lead inside your team, or a fractional CTO above it.
See it →04
Support after launch
Monitoring, security and dependency updates, bug triage and fast response when something breaks.
See it →