Question 1

What is a pre-flight scoping call?

Accepted Answer

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.

Question 2

Where are you located and what timezone do you work in?

Accepted Answer

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.

Question 3

How do I get started with Precode?

Accepted Answer

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.

Question 4

Do you offer a guarantee?

Accepted Answer

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.

Question 5

Why do you call it "pre-flight" and not "kickoff"?

Accepted Answer

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.

Question 6

How do I book a sprint?

Accepted Answer

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.

Question 7

What's the guarantee on a UX Sprint?

Accepted Answer

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.

Question 8

Do you work remotely or in person?

Accepted Answer

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

Question 9

What's the guarantee on a V1 Sprint?

Accepted Answer

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.

Question 10

How do we communicate during a project?

Accepted Answer

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

Question 11

What is a show-and-tell?

Accepted Answer

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.

Question 12

What's the first step?

Accepted Answer

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.

Question 13

Do you offer refunds?

Accepted Answer

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.

Question 14

How do I contact Precode?

Accepted Answer

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

Question 15

What is the handover?

Accepted Answer

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.

Question 16

How far in advance do I need to book?

Accepted Answer

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

Question 17

How involved do I need to be during a sprint?

Accepted Answer

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.

Question 18

Can you start quickly?

Accepted Answer

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.

Question 19

What if I'm not happy with the result?

Accepted Answer

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.

Question 20

What's your email address?

Accepted Answer

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

Question 21

Do I have to sit in a room with you all week?

Accepted Answer

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

Question 22

Do you sign contracts?

Accepted Answer

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

Question 23

How do I know you won't overrun or overcharge?

Accepted Answer

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

Question 24

Can I just email instead of booking a call?

Accepted Answer

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

Question 25

What happens on the Friday before the sprint?

Accepted Answer

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

Question 26

What if the project drifts from the brief?

Accepted Answer

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.

Question 27

What should I prepare before the first call?

Accepted Answer

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.

Question 28

Will my project be confidential?

Accepted Answer

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

Question 29

How quickly will you respond?

Accepted Answer

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

Question 30

How do you keep a sprint on track?

Accepted Answer

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.

Question 31

What do you need from me to start?

Accepted Answer

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.

Question 32

How can you be so confident in five days?

Accepted Answer

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.

Question 33

What if the project goes off track mid-week?

Accepted Answer

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.

Question 34

How many clients do you take on at once?

Accepted Answer

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

Question 35

Can I see examples of your work first?

Accepted Answer

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

Question 36

What's the risk compared to a long agency engagement?

Accepted Answer

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.

Question 37

Why are sprints so much faster than agencies?

Accepted Answer

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.

Question 38

What if I'm not sure which service I need?

Accepted Answer

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.

Question 39

What if my project needs more than five days?

Accepted Answer

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.

Question 40

How do I know your work is good before I commit?

Accepted Answer

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

Question 41

Can we do a trial before committing to a big project?

Accepted Answer

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

Question 42

Do you scope honestly, or overpromise to win the deal?

Accepted Answer

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.

Question 43

Do you offer a free consultation?

Accepted Answer

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.

Question 44

What information do you need before a sprint?

Accepted Answer

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.

Question 45

Do you offer reference calls with past clients?

Accepted Answer

Yes — just ask during the sales process.

Question 46

What happens after I get in touch?

Accepted Answer

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.

Question 47

Can you handle projects with lots of stakeholders?

Accepted Answer

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.

Question 48

What happens at the very first conversation?

Accepted Answer

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.

Question 49

What does a typical week of a V1 Sprint look like?

Accepted Answer

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.

Question 50

Is the intro call a sales pitch?

Accepted Answer

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.

Question 51

Do you provide documentation?

Accepted Answer

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.

How a sprint works