Discovery sprint: two weeks to a plan you can trust.
Founder-led. You work directly with Rizwan Mansuri, with senior associates brought in when the work needs them. Before you commit a budget, we audit your idea or codebase, pick the right Python stack and give you a scope, estimate and roadmap your team can execute with or without us.
Fixed scope2 weeksTwo weeks. Includes a working prototype on real data and a go or no-go decision.Book a discovery sprint
How the two weeks run
Days 1–2InterviewsStakeholders, users and engineers. We learn the goal, the constraints and where it hurts today.
Days 3–5AuditArchitecture, data and code review. For existing apps, a dependency and upgrade-risk report.
Days 6–8PrototypeA thin vertical slice on your real data, to prove the hardest part works.
Days 9–10PlanScope, estimate, roadmap and a go or no-go recommendation, presented to your team.
What you walk away with
Every document is yours to keep. If you take the plan to another team, that's fine.
01Architecture recommendationDjango, FastAPI or both, with hosting, data and integration choices explained.
02Scoped backlogFeatures broken into four-week cycles, ordered by value and risk.
03Estimate and cost envelopeA range you can take to your board, with the assumptions written down.
04Working prototypeCode in your repository, running on real data.
05Upgrade or risk reportFor existing codebases: what to fix first and what can wait.
06AI evaluation planIf AI is in scope: model choice, test set and cost per thousand calls.
Who it's for
CTOs and engineering leadsPlanning a new product or a major rebuild and want a second opinion before committing.
Startup foundersNeed a credible plan and estimate for investors before hiring a team.
Public sector teamsNeed a documented discovery that fits the GOV.UK Service Standard.
AgenciesPitching a Python build and need a technical partner to scope it.
Discovery questions
What happens after the discovery?
You decide. Most clients continue into four-week build cycles. Some take the plan to their own team.
Is the prototype thrown away?
No. It runs on your real data in your repository, so it carries straight into the build if you continue.
Do you need access to our codebase?
For upgrades and rescues, yes, read-only is enough. For new products we work from your requirements and data.
Can it run remotely?
Yes. We work remote-first across UK, EU and US hours.
Analytics cookies
We'd like to use Google Analytics to see which pages are useful. Nothing is set unless you allow it. Cookie policy