brand.software(process)
From first idea to launch, with no surprises.
You always know what is being built, what it costs and what comes next.
Why the process matters
Software projects rarely fail in one dramatic moment. They fail quietly: a scope nobody wrote down, a design nobody saw until it was built, a change that nobody priced, a security question asked a week before launch. Our process exists to bring those moments forward, while they are still cheap to fix.
Each stage below ends with something you can look at and respond to. You never have to take progress on trust.
1. Price and scope
You start by answering a short form, and you see a live price as you go. The form asks what kind of software you need, which features matter and what timeline you want. It is quick, and it gives us a far better first conversation than a blank email.
We then review the scope with you. This is where we ask what the software must do, who will use it, what it has to connect to and what you want to change in the business once it exists. If your request goes beyond what the form covers, we discuss it rather than guess. The result is a final quote in writing, and nothing is binding before it.
2. Architecture
Before anyone designs a screen, we decide how the system is put together. Where does the data live? Which parts talk to which? What happens when you add a second location, a new kind of user, or a mobile app next year?
Getting this right early is what keeps software changeable later. It is also where we plan security, payments and permissions, so they are part of the foundation rather than something attached at the end.
3. Design
We map the screens and the journeys of everyone who uses the product, so you can react to it before code is written. Customers, staff and administrators often need very different views of the same system, and we plan for each.
Changing a screen on paper is far easier than changing it once it is built, so this is the best time to speak up. If something feels wrong, it almost certainly is, and now is when fixing it costs least.
4. Build in stages
Work is delivered in stages you can open and test. A stage is a working preview, not a slide deck. Your client portal shows each milestone, its previews, files and messages in one place, and you approve work there.
Plans change, and that's normal. If you want something outside the agreed scope, raise a change request from the portal. We reply with a price and a delivery time, and nothing starts until you approve. You always know what the project costs, even after it has moved.
5. Test and secure
Before anything goes live, we test the main flows, permissions, payments and performance across devices. We check that each person can see and do only what their role allows, that prices and payments are verified on the server, and that pages stay fast on a phone.
Payments run through the provider's own hosted checkout, so the software never stores raw card numbers. Sensitive actions are logged, so there is a record of who changed what.
6. Launch
We deploy, watch the launch closely and fix what real use reveals. Real people always find a path nobody predicted, and the first days are when we pay most attention.
Where a project calls for it, launch also covers moving your data across and training your team, as set out in your scope. App store submission is part of mobile app projects.
7. Support and grow
After launch you can keep us on a support plan for hosting, monitoring, updates, backups and small changes. New features can continue in further stages, each scoped and quoted the same way.
If you want customers for what we built, our marketing team works in the same company and can plan campaigns around it.
How long does a software project take?
Honestly, it depends on the scope, which is why we confirm timing with your quote rather than publish a general figure. A focused website and a multi-role business system are very different jobs. Some forms offer a rush option, which adds a percentage to the project and is shown before you choose it.
The biggest factor you control is feedback. Projects move fastest when one person can answer questions and approve stages promptly.
How we communicate during a project
Everything about your project lives in the client portal: milestones, previews, files, messages and change requests. You can book a video call from there whenever a conversation is faster than a message. Decisions are written down where everyone can see them, so there is never a debate later about what was agreed.
What we need from you
- One person who can answer questions and make decisions
- Your content, brand files and access to any tools we connect
- Feedback at each review, so problems surface early
- Honest detail on how the work happens today, including the messy parts
What you can count on from us
- A written quote before work is binding
- Previews you can open at every stage
- A price and delivery time for every change, before it starts
- One place, the client portal, for files, messages and decisions
- Plain language instead of jargon
Next step
Start with the form. It takes a few minutes, shows a live price, and gives us what we need for a useful first conversation.
How long will my project take?
It depends on the scope, so we confirm timing with your quote rather than quote a general figure. Some forms offer a rush option at an added percentage.
Can I change my mind during the build?
Yes. Send a change request and we reply with a price and delivery time. Nothing starts until you approve it.
Will I see the work before launch?
Yes. Work is delivered in stages you can open and test, with progress shown in your client portal.
Do you move our existing data?
Where your scope includes it, yes. Data migration and team training are agreed in the quote.