Precode (@weareprecode) header
Precode (@weareprecode) profile picture

Plug your company into a world-class digital product design team. Strategy, UX design, rapid prototyping and more. In just 5 days.

Brighton
Joined October 2016
Photo by Precode (@weareprecode)Photo by Precode (@weareprecode)
Two sprints. Ten working days. Idea to live product. Week one: UX Sprint. Production-ready designs and a tested Figma prototype. You know the design works before a line of code is written. Week two: V1 Sprint. Working deployed web application built from those designs. Real users can use it by Friday. Not a simulation. Not a mockup. A live product with real users giving you real behaviour data. That's the pipeline. Design right first. Build fast second. Most product teams take 6-9 months to get from idea to user feedback. This is 10 days.
23
A UK Supermarket needed a member services product built. Not designed. Built. Working application. Real users. Real functionality. V1 Sprint. One week. Deployed to staging by Friday. Clean codebase. Their internal team could extend it from there. That's the V1 Sprint model. We build the foundation and the core features. You own the code. Your team takes it forward. No handover complexity. No proprietary frameworks. Standard stack: Next.js, TypeScript, Supabase, Vercel. Every competent developer can work with it.
11
What you get from a 5-day UX Sprint: Complete user flows and wireframes. High-fidelity UI integrated with your existing design system. Interactive Figma prototype ready for user testing or stakeholder sign-off. Developer-ready specs and annotations. Exported assets ready for engineering handoff. Delivered Friday afternoon. Total client time across the week: approximately 5 hours. This is not a Google Design Sprint. You don't attend workshops. You don't facilitate sessions. We design. You review the daily video updates. That's it. £10,000 + VAT. One week. No internal resource burned getting there. If that sounds useful, start with a scoping call.
11
The question we ask on every scoping call: What has to be true for this idea to work? Not: what features do you want? Not: what does your roadmap say? What is the single assumption, if wrong, that makes the whole thing collapse? That assumption becomes the sprint. Every decision about what to design or build flows from that one question. It's also why we can deliver production-ready work in 5 days. We're not trying to solve everything. We're trying to test the one thing that matters most. Most backlogs are full of features. Most backlogs don't have a clear answer to that question.
2
Fixed price. Fixed timeline. No surprises. Every sprint is scoped upfront. You know what you're getting before we start. You know what it costs before we start. No extensions. No "this took longer than expected". No change requests that double the invoice. 5 days. Production-ready output. Delivered Friday. UX Sprint: £10,000 + VAT. Complete designs, Figma prototype, developer specs. V1 Sprint: from £10,000 + VAT. Working deployed web or mobile app. If you've ever been burned by a variable scope engagement, you'll understand why fixed pricing matters.
3
We quoted a sprint to a client who had just come off a call with a traditional agency. The agency's proposal: 12 weeks. Discovery phase, design phase, review cycles, stakeholder sign-off process baked into the timeline. Our proposal: 5 days. One kickoff call. Daily video updates. Designs delivered Friday. Same brief. Different model. The difference isn't capability. It's how we work. No account managers. No juniors learning on your project. Two senior founders doing the actual work. That's what on-demand senior product team actually means.
5
The V1 Sprint is not a prototype. It's not a clickable mockup. It's not a Figma file dressed up to look like a product. It's a deployed web application. Working code. Real users can sign up, complete actions, and give you actual behaviour data. In 5 days. Authentication, database, core features, deployed to staging. Clean TypeScript codebase your own engineers can pick up and extend. From £10,000 + VAT for the web ot iOS / Android application. If you have a validated idea and you need working software fast, that's what the V1 Sprint is for.
6
What a 5-day UX Sprint actually looks like: Pre Sprint: we take your brief on a 1-2 hour kickoff call. Monday to Friday: we design. You get a 6pm video each evening showing progress. Friday: we hand over production-ready designs, a working Figma prototype, and developer specs. Your total time investment across the week: roughly 5 hours. No workshops. No facilitated sessions. No post-it notes. We do the design work independently. You review. That's the whole process. £10,000 + VAT. Fixed price. Fixed timeline.
10
Your engineering team is not the problem. They're shipping. They're executing. They're heads down on the roadmap. The problem is the list of good ideas that never make it onto that roadmap. Features that would genuinely move the needle. Experiments worth running. Bets worth taking. Sitting in a backlog. Ageing. Losing momentum. Not because they're bad ideas. Because there's no capacity to test them without pulling engineers off something already committed. That's the trap. And most product teams just accept it.
2
The uncomfortable truth about AI development tools: They make good decisions faster. They make bad decisions faster too. You can now build the wrong thing in record time. Saw a team ship a complete feature in 48 hours using AI. Impressive execution. Zero user demand. Reverted within a week. The tools have changed. The need to validate hasn't.
2
What's the most expensive assumption you've seen a team get wrong? I'll start: watched a fintech build for 9 months assuming enterprise clients would self-serve onboarding. They needed white-glove support. Every. Single. Deal. Complete architecture rebuild.
2
We don't run workshops. No post-it notes. No voting exercises. No facilitation theatre. We take your brief, disappear for 5 days, and come back with working software that real users can test. The difference matters. Workshops produce alignment documents. Sprints produce answers.
1
Question for product leads: How many features in your current backlog have been validated with real user behaviour (not just interviews)? Be honest.
How we compress discovery from weeks to hours: → Skip the stakeholder alignment workshops → Ask one question: what has to be true for this to work? → Build the thing that tests that assumption → Put it in front of users by day 3 Most "discovery" is just avoiding the discomfort of being wrong. Faster to build something small and be wrong than debate endlessly and never know.
2
Hot take: your detailed product roadmap is probably your biggest liability right now. Markets shift monthly. AI capabilities change weekly. A 12-month plan built on assumptions from January is already outdated. Ship, learn, adjust. Repeat.
1
The AI tools we actually use in Build Sprints: → Claude for architecture decisions and complex logic and rapid implementation → Figma for UI What we DON'T use AI for: → Deciding what to build → Judging if the UX actually works → Interpreting user feedback AI accelerates execution. It doesn't replace judgment. The teams getting burned are the ones who forgot that second part.
1
16
Client arrived with 23 features they wanted. We asked one question: "Which of these could kill the product if you're wrong about it?" 22 features went to the backlog. 1 became the entire sprint focus. By Thursday, they had their answer.
Unpopular opinion: most startups don't have a building problem. They have a validation problem. AI makes it trivially easy to ship code. Cursor, Claude, Codex - any competent developer can build faster than ever. But building faster doesn't mean you're building the right thing faster. I've watched teams use AI to ship a 3-month roadmap in 6 weeks. They were thrilled. Then they launched to crickets. Same bad idea, just executed more efficiently. The bottleneck has shifted. Speed is no longer the differentiator. Judgment is.
44
What's the longest you've waited to get user feedback on a new feature? Curious what's normal for teams right now.
The hardest part of building an MVP isn't the code. It's deciding what NOT to build. Every feature you add extends your timeline. Every assumption you don't test increases your risk. We've shipped dozens of MVPs in 5 days. The constraint forces clarity. Here's the framework we use to cut ruthlessly: 1. What's the riskiest assumption? 2. What's the minimum needed to test it? 3. Can a user complete the core action? If a feature doesn't serve these three questions, it gets cut. No exceptions. The 5-day deadline isn't arbitrary. It's a forcing function that eliminates scope creep before it starts.
3