No, you do not need a spec before you start. At Bamco you describe the idea or the problem in plain language, and turning that into a scoped, buildable plan is the architecture step, not something you have to bring. Writing the spec yourself would often lock in the wrong solution before anyone has thought it through, which is exactly the work you are hiring the senior team to do.
Information current as at 4 July 2026
Many owners hold off because they think they need a polished specification before anyone will talk to them. You do not. A scoped plan is what the architecture step produces, not what you have to arrive with. Describing how your business runs and where it frustrates you, in ordinary language, is enough to begin. The technical shape of the answer is the job you are paying for, so being asked to bring it fully formed would defeat the point. The plan comes out of the conversation, not before it, and holding off until you have written one only delays the work that produces it.
When a non-technical owner writes a full spec, it often quietly locks in the wrong solution. The document describes a feature the owner imagined rather than the outcome the business needs, and once it is written down it becomes the thing everyone builds toward, right or wrong. A good senior team works backward from the problem, not forward from a guessed answer, which sometimes means the best system looks nothing like the spec you would have written. Coming in with an open description of the problem leaves room for the better answer to surface.
Bring us the idea you already have, or book an audit and we map where the money is leaking. Either way, you deal directly with the senior team that designs and builds it.
The path is the same whether you arrive with a detailed idea or a vague frustration: you voice it, Bamco architects it, and you receive a fixed-scope proposal with a firm number before anything is built. The architecture step is where the rough idea is mapped, sized and turned into something buildable, with the real-world cases that break a naive version already accounted for. You deal with the senior team directly through all of it, so there is no game of translating your intent through layers of people. If a written brief helps you think, it is welcome, but it is never a requirement.
Whether you can name exactly what you want built, or you just know something is leaking, the next step is the same conversation.