How we work
Work with Code + Carbon through direct conversations, concrete decisions, and regular reviews. Know what we’re building, what you’re investing in, and what happens next.
See how a project unfoldsDEFINE
We talk through the goal, the people using the product, and what is getting in the way. Bring your priorities, existing tools, and any budget or timing constraints.
WHAT YOU LEAVE WITHA focused scope, proposed cost, and milestones.
DESIGN
Review the page structure, key screens, or a prototype. Your feedback helps us resolve the important decisions while changes are still easy to make.
WHAT YOU LEAVE WITHAn agreed direction and the key user journeys.
DEVELOP
We build in reviewable stages and test the journeys your customers and business rely on. You try working features, share feedback, and agree on the next step.
WHAT YOU LEAVE WITHTested features, review checkpoints, and visible progress.
LAUNCH
We check launch readiness together, put the agreed access and guidance in your hands, and confirm who looks after what once the product is live.
WHAT YOU LEAVE WITHA launch checklist, handover, and agreed support arrangements.
BEFORE WE GET STARTED
A good project starts with a shared understanding. We put the commitments in writing, including what is included and what will be scoped separately.
YOUR PROJECT AGREEMENT
A FEW PRACTICAL QUESTIONS
No. Tell us what you want to build or improve, who it is for, and what a useful result would look like. We can help turn that into a project scope.
We propose a cost against an agreed scope and deliverables before development starts. Share your budget early so we can prioritize a useful first version. Hosting, third-party services, and ongoing support are identified separately where they apply.
We plan milestones around the scope, integrations, content, and review time. The proposal sets out those dependencies and your responsibilities, so you can see what the schedule relies on.
We discuss the effect on the work, price, and milestones before agreeing a change. New ideas can become part of the current scope or a later release.
Yes. We review the existing website or application first, then recommend focused improvements or a rebuild where the condition of the system calls for one.
Ownership, source-code access, third-party licenses, and account responsibilities are set out in the project agreement. We also define the handover and any ongoing maintenance or improvements you would like us to support.
