How we work with you.
No surprises. No vague promises. Clear stages from conversation to launch. Everything important gets discussed and confirmed in writing.
No Impossible Promises
Our process is designed to be honest, clear, and realistic. We don't make promises we can't keep. We scope carefully. We build in stages so you see progress. We launch when we're confident it works.
Every project is different. Websites have different needs than web apps. Simple projects move fast. Complex ones need proper planning. We explain what's realistic for your situation.
The Seven Steps
First Conversation
We talk about your business, what you need, and what success looks like. No pressure. No sales pitch. Just understanding.
Duration: 1 call, 30–60 minutes
Scope & Priorities
We define what's in, what's out, what's optional. We rank features. We talk timeline and budget. Nothing vague.
Duration: 1–2 weeks (for simple projects)
Written Proposal
We send a proposal with scope, timeline, price, and what's included. You review, ask questions, sign. Everything in writing.
Duration: Few days for your review
Build (Staged)
We build and show you work frequently. You give feedback. We incorporate it before the next stage. You're not surprised at the end.
Duration: Varies by project (weeks for websites, months for apps)
Review & Feedback
You review the complete work. We fix issues, make refinements. One main round of changes is included.
Duration: 1–2 weeks
Launch
When everything works, we deploy to production. Your domain, your hosting, your control. We verify everything is live and working.
Duration: 1 day
Support & Handoff
We're available if questions come up. We explain how to update content. Ongoing support available if you want it.
Duration: Ongoing
Why Written Agreements Matter
A handshake is friendly. A written proposal is professional and protects everyone.
- No surprises: Everyone knows what to expect—scope, timeline, price.
- Clarity on changes: If scope changes, we discuss it, not surprise you with extra costs.
- Reference point: If either of us needs to remember what was agreed, we have it in writing.
- Professional: It shows both of us are serious and organized.
Why Discovery Matters for Complex Projects
For simple websites, we can move fast. For web apps, custom systems, and integrations, discovery saves time and money later.
Good discovery prevents expensive mistakes.
Building the wrong thing is slower than building the right thing carefully.
During discovery, we ask:
- • How does your business actually work?
- • What tools do you use? What data do they contain?
- • Where does it hurt? What takes the most time or causes errors?
- • Who will use this? What do they need to do?
- • What happens if something breaks?
- • What's success? How will you know it's working?
This takes time. For complex projects, it's 1–4 weeks of planning before we write a line of code. That planning pays for itself many times over.
Ready to start?
Let's have that first conversation and see if we're a good fit.
Start a Projecthello@fieldops.uk