How we work
A clear path from first conversation to launch, and beyond
You should always know what is being built, who is working on it and what happens next. Here’s the whole customer experience, step by step.
Six stages
What happens at each stage
- Stage 1
Discovery
What you see
A conversation about your challenges, goals, budget and what is realistically achievable.
What CoxLume does
Identify scope, risks and who makes decisions on your side.
- Stage 2
Proposal
What you see
A written outcome, deliverables, assumptions, fees and milestones you can review.
What CoxLume does
Estimate the effort with the technical lead before committing to numbers.
- Stage 3
Agreement
What you see
A signed agreement covering payment schedule, ownership, change control and approved team access.
What CoxLume does
Confirm who may access which systems, including any authorized team members.
- Stage 4
Design & Build
What you see
Design reviews, regular progress updates and working demos.
What CoxLume does
Approved developers work within the permitted scope; the founder reviews the work.
- Stage 5
QA & Launch
What you see
Testing evidence, your acceptance and a deployment plan.
What CoxLume does
Test, correct issues and release only with your approval.
- Stage 6
Ongoing Support
What you see
Handover, documentation, an optional maintenance plan and planned enhancements.
What CoxLume does
Respond according to the signed support terms.
Delivery model
U.S. leadership, approved technical team
CoxLume coordinates client relationships from the U.S. and may involve approved technical team members, with disclosure and approvals appropriate to each engagement.
Disclosed up front
You know who is on the team before you sign anything.
Your approval required
Additional team members join a project only with your written authorization.
Scoped access
Access is limited to what the agreed tasks need and removed afterwards.
One accountable contact
CoxLume remains responsible for communication, review and delivery.
Client data
How we protect your information
Plain answers, and no compliance badges we haven’t earned.
Only people you approve. CoxLume coordinates client relationships from the U.S. and may involve approved technical team members. Before any engagement that involves your systems or data, we tell you who will be involved and what they will be able to access, and you decide.
Only what a task requires. We prefer separate, revocable credentials for each person, staging environments instead of live data where possible, and removing access when the work is done.
Secrets are never stored in code repositories or shared in plain chat messages. They are kept in the hosting provider’s environment settings or a password manager.
Not at this time, and we won’t display badges we haven’t earned. If your project has formal compliance requirements, tell us early so we can discuss whether we are the right fit.
Working together
What we need from you
Projects go smoothly when a few things are in place on your side. We’ll agree these at the start.
One decision-maker
A named person who can approve designs, content and launch, so feedback doesn’t stall between people.
Content and brand assets
Your logo, colours, photos and the facts about your business. We can help shape the words, but you know your business best.
Timely feedback
Reviews at each milestone. The schedule in your proposal assumes feedback within the agreed review window.
Access when it’s needed
Logins to the accounts the work touches (domain, hosting, existing tools), shared securely and only for the agreed tasks.
When the scope changes
Plans change, and that’s normal. What matters is that no change surprises you on an invoice.
You ask
Any new idea or request is welcome, at any stage.
We estimate
We describe the change and its effect on cost, timeline and anything already built, in writing.
You decide
Nothing outside the agreed scope starts until you approve it. Declining keeps the original plan.
Ownership & handover
What’s yours, and what happens after launch
Who holds the domain, hosting, code, licences and access, and what support does and doesn’t include.
We recommend that the domain, hosting and any paid service accounts are registered in your business’s name, with your billing details. Where we set something up for you, we transfer it to you at handover. The agreement lists each account and who holds it.
Ownership terms are written into your agreement before work begins. Our standard approach is that you own the deliverables you pay for once invoices are settled. The aim is that you can keep running and changing what we build, with or without us.
Fonts, plugins, templates and paid services are identified before you commit, with their costs and terms. Where possible they are licensed to your business, not to us, and they are listed in the handover documents.
Access to the source code repository, the accounts and settings your project uses, and documentation on how it is set up and how to make common changes. Temporary access for our team is removed when the work is done.
Only what your written support plan says: typically agreed updates, fixes and monitoring, with response expectations stated up front. We don’t promise round-the-clock cover unless it has been explicitly agreed and resourced.
It is handled like any other change: we describe it, estimate it, and start only once you approve. Support is optional. You can also take the project elsewhere, and the handover documents are written to make that possible.
Have a project in mind? Let’s make it happen.
Start with a free introductory conversation about your goals. We’ll tell you honestly whether CoxLume is the right fit and what a sensible first step looks like.