The First Fortnight, From the Inside
For a lot of people, commissioning custom software feels like a black box. You agree to it, then wonder what on earth is happening while you wait. It need not be a mystery. The opening fortnight sets the tone for everything that follows, so here is honestly how we spend it, day by day, in plain words.
Week one is mostly us listening
Before anyone writes a line of code, we want to understand your world. How does the work actually flow? Where does it get stuck? What does a good day look like, and what does a bad one feel like? We ask a lot of questions, some of them annoyingly obvious, because the obvious answers are where the real problems usually hide. The goal is simple. Build the right thing, not just a thing.
We sketch before we build
Ideas are cheap and easy to change on paper, and expensive to change in code. So we draw. Rough screens, simple flows, arrows between boxes. You get to look at something and say that is not quite right, which is exactly what we want to hear early. Every misunderstanding we catch on a sketch is one we do not pay for later.
You see something real, faster than you expect
Within the first couple of weeks you will usually have something you can click through. It will not be finished, and parts of it will be held together with sticky tape, but it turns the conversation from abstract to concrete. People react completely differently to something they can poke at than to a document describing it. That reaction is gold.
We argue about scope, in the friendliest way
Here is the honest part. You will want more than the budget allows at first, and that is normal. So we work out together what truly matters for the first version and what can wait. A good partner pushes back here rather than nodding along, because a focused first release that ships beats a perfect one that never does. Our wider piece on the development process picks up the story from here.
By day fourteen you have a plan you can trust
At the end of the fortnight you should not be guessing. You will know what we are building, roughly how long it takes, what it costs, and what the first usable version looks like. The big unknowns have been turned into decisions. From there it is steady building with regular check ins, no nasty surprises, and a clear shared picture of where it is all heading.
Why this matters more than the code
Plenty of projects fail not because the code was bad, but because nobody agreed on what good looked like. A calm, thorough start is the cheapest insurance you can buy. If you are weighing up a project and the process feels foggy, that is worth fixing before anything else. We are always happy to walk you through how we would approach yours.
