Discovery
STEP 01 OF 06We sit with the people who'll use the thing. We map the problem before we sketch a solution.
YOU RECEIVE Discovery brief, scoped questions, named constraints.
§ Process — From first call to support retainer
How we work, step by step.
Six steps. Two-week sprints. Weekly demos. Written decisions. No mystery between Monday and Friday.
§ Steps · 01–06
The shape of an engagement.
Proposal & Planning
STEP 02 OF 06A written proposal: scope, milestones, money, and what we will not be doing. No surprises.
YOU RECEIVE Signed SOW, roadmap with dates, engagement model.
Design
STEP 03 OF 06Architecture and interface, in parallel. Pen and paper before pixels, pixels before code.
YOU RECEIVE Clickable prototype, technical RFC, decisions log.
Development
STEP 04 OF 06Two-week iterations, weekly demos, written decisions. The codebase tells the truth about itself.
YOU RECEIVE Working software at the end of every sprint.
QA & Launch
STEP 05 OF 06Test plans tied to acceptance criteria. Soft launches, dark launches, real launches.
YOU RECEIVE Release notes, runbooks, on-call schedule.
Support & Growth
STEP 06 OF 06We don't disappear after launch. SLAs, monthly reviews, and a plan for the next thing.
YOU RECEIVE Maintenance retainer, growth roadmap, handover docs.
§ Communication — Cadence
You won't have to ask where the project is.
Weekly plan
Written, shared. What we're shipping this week and what we're not.
Demo + notes
Live demo of what moved. Written summary in the channel after.
Shared tools
GitHub, Linear, Figma — full access from day one. Read-only by default, contributor on request.
Single point of contact
One person who'll always pick up. A backup who knows your project just as well.
§ Engagement models
The contract changes shape with the work.
First sprint
Fixed scope, fixed price. Discovery, design, and a thin slice of working software. Decide together what comes next.
2–6 WEEKSProject build
Defined outcome, time-and-materials with a monthly cap. Two-week iterations. You sit in on demos.
3–12 MONTHSDedicated team
Vetted engineers embedded with your team. They join your stand-up. They use your tools. They speak your timezone.
6+ MONTHS§ FAQ — Pre-sales questions
The questions we've heard before.
A first sprint is 2–6 weeks. Long-term builds run three to twelve months. Dedicated teams are open-ended with a 30-day notice on either side.
Read it. Tested? Now let's try it.
Most projects start with a 30-minute call. We listen first, write up notes second.
Email a project brief HELLO@GUESSYOULTD.COM