The Ampersand Method
Six phases. Every one of them has an ampersand.
Most projects do not fail inside a phase. They fail in the gaps between them, where research is handed to design, design is thrown to engineering and launch is handed to nobody. So we closed the gaps. Every phase of our method pairs a way of thinking with a way of making, and the same small senior team carries your product from the first workshop to the years after launch.
Principles
Four promises the method is built to keep.
Our old process sheet already spoke in ampersands: gather information, analysis, designing & blueprint, testing & deployment. We kept the habit and sharpened the idea behind it. These four promises are what the phases exist to protect.
- &
Design and code in the same room.
Engineers sit in the first workshop and designers stay until the last sprint. The architecture is drawn beside the wireframes, so no screen arrives in week nine that nobody can build.
- &
Working software, every week.
Progress is shown, never reported. Every Friday you click what was built that week on a staging site you can open at any hour. If something is off, you find out in days, not at the end.
- &
Decisions in writing.
WhatsApp for speed, written decisions for memory. Anything that moves scope, cost or a date is written down in plain words the same day, with who decided and why.
- &
Launch is the middle, not the end.
We began as a hosting company in 2018, answering support calls ourselves. Care is planned in week one, not sold in the last, which is why most clients keep us on long after go-live.
Six phases. Every one of them has an ampersand.
Our website and app development process
Each phase ends with something you can hold, test or sign. The edges overlap where they should: engineers prototype the risky pieces during Sketch & Shape, and designers review every Build & Break demo. A Discovery Sprint covers the first three phases in three weeks, from ₹3.5 lakh (US$4,000 or AED 15,000). A care plan lives in the sixth for as long as it earns its keep.
Phase 01 · Listen
Listen & Learn
Workshops with your team, interviews with customers and stakeholders, and an honest look at the product, data and systems you already have. Nothing gets designed until we agree what problem we are solving and how we will know it is solved.
- A two sentence problem statement
- Goals and success measures
- Stakeholder and user interview notes
Phase 02 · Map
Map & Measure
We audit content, systems and data, map the journeys that matter, list requirements and risks, and cost the work. You get a scope you can sign and a roadmap that shows what ships first and why.
- Journey maps and requirements
- Risk and dependency list
- A costed roadmap with assumptions
Phase 03 · Sketch
Sketch & Shape
Information architecture, wireframes and clickable prototypes that we test with real users, then visual design and a design system. The engineers draw the architecture alongside, so every screen already has a way to exist.
- Tested clickable prototype
- Visual design and design system
- Technical architecture
Phase 04 · Build
Build & Break
We build in short sprints with code review, automated tests and continuous deployment to a staging site you can click at any time. Quality is not a phase at the end. Someone is actively trying to break the product from the first week.
- Working software every week
- Automated test suite
- Staging environment you can use
Phase 05 · Launch
Launch & Land
Before launch we check speed, security and accessibility, run user acceptance with your team, migrate content and train the people who will own the product. Go-live is rehearsed, so launch day is calm.
- Launch checklist and runbook
- Trained product owners
- Performance and accessibility report
Phase 06 · Care
Care & Grow
We host and monitor, respond to issues within agreed times, watch the analytics, improve search visibility and run experiments. Every quarter we review the roadmap with you and decide what earns a place next.
- Monitoring and support with response times
- Monthly performance notes
- Quarterly roadmap review
Rituals
A rhythm you can set your calendar by.
Good projects feel predictable from the client's side of the table. These five habits run on every engagement, whether you are in Mumbai, Dubai or London.
Every Monday
Plan the week
A thirty minute call to agree the week's goals, the open questions and anything we need from you. The plan is written up and in your inbox before lunch.
Every Friday
Demo working software
The people who built it show it, on the staging site or on a real phone, never in slides. You click, question and decide what changes. In Mumbai the demo usually wraps up just before chai at four.
Every week
The written update
One page, sent on Friday evening: what shipped, what slipped and why, decisions made, risks rising and budget used against plan. Short enough to forward to a board member who missed the demo.
Every month
The metrics review
Once the product is live, we sit down with the numbers that matter to your business: conversion, speed, uptime, support tickets and search visibility. Each review ends with one or two changes worth making.
Every quarter
The roadmap review
Half a day with a partner to step back and ask what the product achieved, what the market changed and what earns a place next. Sometimes the honest answer is to build less.
An example
What 12 weeks of a Product Build looks like.
An illustrative plan for a new customer web app, the kind of Product Build that starts from ₹12 lakh (US$15,000 or AED 55,000). Your weeks will differ. The rhythm will not.
| When | Phase | What happens |
|---|---|---|
| Week 1 | Listen & Learn | Kick-off workshop with your team, customer and stakeholder interviews, and a look at the systems and data you already have. The week ends with the problem written in two sentences. |
| Week 2 | Map & Measure | Journeys, requirements and risks mapped. The release plan is agreed and the estimate reconfirmed, with every assumption in plain view. |
| Week 3 | Sketch & Shape | Wireframes and a clickable prototype tested with real users, the first visual design and a technical architecture the engineers have already signed off. From here, design runs one sprint ahead of the build. |
| Weeks 4 to 5 | Build & Break | Sprint one: environments, accounts, core data and the first complete journey working end to end. The first Friday demo is real software. |
| Weeks 6 to 7 | Build & Break | Sprint two: the main features and the integrations that carry risk, such as payments or your CRM. Designers refine screens against real content, not placeholder text. |
| Weeks 8 to 9 | Build & Break | Sprint three: the remaining features, admin tools, analytics events and automated tests on every critical path. |
| Week 10 | Build & Break | Feature freeze. The whole team, designers included, spends the week trying to break the product on cheap phones, slow connections and odd inputs, then fixes what they find. |
| Week 11 | Launch & Land | Performance, security and accessibility checks, user acceptance with your team, content loaded, owners trained and a full rehearsal of go-live. |
| Week 12 | Launch & Land | Go-live early in the week, a close watch through the first days and the runbook handed over. If launch day feels uneventful, the plan worked. |
| Week 13 onwards | Care & Grow | Monitoring, support with agreed response times, the first monthly metrics review and the list of good ideas that did not make version one. |
Tools we use, chosen to stay out of the way.
If your team already has its tools, we work in yours. If not, this is our default kit, and you hold admin access to every account from the first day.
- Research and design
- Figma and FigJamMaze for prototype testingMicrosoft Clarity for session insightAccessibility plugins and contrast checks
- Planning and communication
- Linear or JiraNotion for decisions and documentationSlack or Microsoft TeamsWhatsApp for quick questionsGoogle Meet or Zoom
- Engineering
- GitHub with reviewed pull requestsNext.js, React and Node.jsLaravelFlutter and React NativeContinuous deployment to staging
- Quality and launch
- Playwright automated testsReal device testing on iOS and AndroidLighthouse and Core Web Vitalsaxe accessibility auditsSentry error tracking
- Hosting and care
- AWSCloudflareVercelGrafana and uptime monitoringGA4 and Search Console
FAQ
Questions we hear often
What are the steps of website development at D&C?
Six phases: Listen & Learn, Map & Measure, Sketch & Shape, Build & Break, Launch & Land and Care & Grow. In plain terms that is discovery, planning, design, build and testing, launch, then ongoing care. Designers and engineers work through all six together. Our web design and development page shows how this plays out for websites and web apps.
How long does discovery take before design starts?
Usually three weeks. A Discovery Sprint covers the first three phases and costs from ₹3.5 lakh (US$4,000 or AED 15,000). You leave with a two sentence problem statement, a tested prototype and a costed roadmap you can take to any builder, including us.
How long does it take to build a website or an app?
A focused business website usually takes 6 to 10 weeks from the first workshop to launch. A first release of a web app, like the example above, takes around 12 weeks, and larger platforms take three to six months. A mobile app for iOS and Android usually needs 12 to 20 weeks after discovery. See mobile app development for the detail.
Is your process agile or fixed price?
Both, each where it fits. Discovery Sprints are a fixed fee. Product Builds are priced against a signed scope, with two week sprints inside it so priorities can move without renegotiating the contract. Embedded Teams are billed monthly. Our engagement models set out the starting points.
What do you need from our side?
One person who can make decisions and give an hour a week to the Friday demo, answers to open questions within a working day or so, and access to the people, data and systems we need to learn from. The better we can hear from your customers, the better the product.
Can we skip phases or join partway through?
Yes. If you arrive with research and designs, we review them in a few days and start at Build & Break. If you have a live product that needs looking after, we begin in Care & Grow with a short audit. Every phase still happens. What changes is how long it needs. The how to brief a studio guide helps you decide where you stand.
Tell us which phase you are in.
Bring the rough version. A partner will tell you where we would start, how long it should take and what it might cost, within one working day.