How a sprint works

A scoping session (usually 60–90 minutes, half a day for complex projects) on the Friday before your sprint. We define the challenge, agree deliverables, confirm the technical approach and give you a firm price and timeline, so there are no surprises.

We're a UK company based in Brighton, working UK hours — same-timezone for UK clients and good overlap with the EU and US East Coast.

Book an intro call at precode.co/call or email hello@precode.co. We'll do a quick fit check, then a pre-flight scoping call to define your project.

Yes. If at the end of Day 5 you don't have what we agreed in the pre-flight call — production-ready designs, or working deployed software — we keep working at no extra charge until you do.

It's how we talk: pre-flight, not kickoff or discovery; show-and-tell, not status update; handover, not deliverable transfer. The language reflects a focused, no-ceremony way of working.

After the pre-flight scoping call, we send an invoice (50% upfront for sprints, 100% for a 1-Day Sprint), confirm your start date, and you're booked.

If at the end of Day 5 you don't have production-ready designs that match what we agreed in the pre-flight call, we keep designing at no additional charge until you do.

We work remotely, with short daily calls and evening show-and-tells. No travel or office time is needed for a sprint to work.

If at the end of Day 5 you don't have working, deployed software that does what we agreed in the pre-flight call, we keep building at no additional charge until it does.

Short morning calls or standups, evening show-and-tells, and Slack for Subscription clients. Communication is high-signal and low-ceremony.

A daily progress update every evening — a prototype link or working URL plus a video or screen recording walkthrough. You see real progress every day and can course-correct in real time.

A short intro call to check fit. If we're a match, we book the pre-flight scoping call where we define the challenge and give you a firm price and timeline.

The guarantee is that we keep working until we deliver what was agreed, rather than a money-back refund. It's scoped to what was agreed in the pre-flight call.

Email hello@precode.co, book at precode.co/call, or contact Ben directly at ben@precode.co for sales.

A live walkthrough at the end of the sprint where we hand over all files or the deployed software and documentation, and answer every question. No surprises.

Sprint slots typically book two to three weeks out, so it's worth planning around any deadline — a raise, board meeting or launch.

For a UX Sprint, about five hours across the week. For a V1 Sprint, a 15-minute morning standup each day plus the evening demo. Your availability keeps things aligned and removes slow back-and-forth.

We can often move fast, but slots usually book two to three weeks ahead. We start on a Monday after a pre-flight call the Friday before.

You see progress every day, so misalignment is caught early, not at the end. If we haven't delivered what we agreed, we keep working until we do.

General enquiries: hello@precode.co. Sales: ben@precode.co.

No. We work independently and show you progress every evening. You steer with short calls and reviews rather than all-day workshops.

The pre-flight scoping call produces a clear, fixed-price scope. We can put NDAs and agreements in place as needed — raise them early.

Fixed price, fixed scope, agreed before you pay. The price doesn't move as the project goes.

Yes — email hello@precode.co with what you're building and we'll take it from there.

The pre-flight scoping call: we lock the challenge, deliverables, technical approach, start date and communication plan, and confirm which service fits.

Daily show-and-tells mean drift is visible on Day 1 or 2 and corrected immediately. Everyone looks at the actual interface or working software, so there's no gap between expectation and delivery.

A sense of what you're building and why now, who the user is, your timeline, whether you have developers, and your rough budget. That's enough for us to assess fit fast.

Yes. We regularly work on confidential and skunkworks projects, sometimes under NDA.

We reply quickly to enquiries. Bear in mind sprint slots usually book two to three weeks out, so flag any deadline early.

Daily show-and-tells mean any drift is caught on Day 1 or 2, not Day 5. Everyone looks at the same thing — the actual interface or working software — so there's no gap between what people imagine and what gets built.

A clear sense of what you're building and why, who the user is, what success looks like, any brand or technical constraints, and availability for short daily check-ins.

We've done it 90+ times. We scope honestly, show progress daily, and keep the scope fixed — so the outcome is high-certainty, not a gamble.

You'll see it in the daily show-and-tell and we course-correct immediately. The structure is designed so you're never surprised at the end.

One at a time during a sprint week — your project gets our full focus. We're deliberately selective so quality never gets diluted.

Yes — see precode.co/work for case studies and precode.co/labs to use products we've built ourselves.

Far lower. £10,000 for a guaranteed outcome in a week, versus tens of thousands over months with no guarantee of what you'll get.

Traditional agencies take eight to twelve weeks because they're structured to keep people busy — account managers, hierarchies, meetings about meetings. Remove that organisational drag and focus two senior people on one problem, and you produce better work faster. Speed comes from cutting the noise, not corners.

That's what the intro and pre-flight calls are for. Tell us the problem and we'll recommend the right service — sometimes that's a single 1-Day Sprint, sometimes a sequence of sprints.

We'll tell you honestly in the pre-flight call whether it's a one-, two- or three-sprint job, and scope it before you pay.

Use our products at precode.co/labs, read the verified reviews on Clutch, and ask for a reference call. The proof is checkable.

Yes — the 1-Day Sprint at £1,500 is built for exactly that.

We scope honestly in the pre-flight call. If a project is a two- or three-sprint job, we say so before you pay. No bait-and-switch.

The intro call and pre-flight scoping call are working conversations that give you real value — clarity on scope, timeline and approach — even if you don't go ahead.

Your goals and why now, who the end user is, what success looks like, what you've tried, who the decision-makers are, your timeline, and any brand guidelines, design systems or technical constraints.

Yes — just ask during the sales process.

A quick fit check, then a pre-flight scoping call, then a fixed-price scope and start date. Sprints start on a Monday after a Friday pre-flight.

Yes, but decisions need to move quickly. The model suits teams who can decide without long committee approval cycles; daily show-and-tells help you keep leadership informed.

A quick fit check: what you're building, your timeline, whether you have developers, your budget range and who's deciding. If it's a fit, we book a pre-flight scoping call.

A 15-minute morning sync on what shipped yesterday and what's next, building all day, and an evening demo with a working URL and screen recording. By Friday it's deployed and handed over.

It's a working conversation. Even if you don't go ahead, you'll leave with clarity on scope, timeline and what "production-ready" really means.

For V1 Sprints, yes — API docs, database schemas, setup instructions, an architecture overview and a video walkthrough. For UX Sprints, you get the design system and production-ready files.