How we work
Scope agreed before the first line.
Software projects usually fail from a missing agreement, not from missing code. That is why the most important stage of our process happens before any development.
The four stages
From spreadsheet to system in use.
Discovery
A conversation with the people who execute, not only with the ones who decide. We map the process as it happens today: where it jams, what is manual, what gets lost, who depends on whom. No cost, no commitment.
Fixed scope
Modules, deliveries, timeline and price agreed in writing before development starts. What stays out is listed too. Mid-project surprises usually come from a badly agreed scope.
Staged build
The project is split into dated deliveries. You use the first while the second is being built, and correct course while correcting is still cheap.
Assisted rollout
Migration of the data living in spreadsheets, team training and direct support from whoever built it. The system is only handed over once the operation is running on it.
Included in every project
Investment
How the price is set.
We do not work from a price list because no two processes are alike. The price comes from the scope, and the scope comes from discovery. What we can say upfront is the format: a build fee, split across the stages, and an optional monthly maintenance covering hosting, database, backup, support and system evolution.
Build
A fixed price set in the scope and split across deliveries. You pay as you receive.
Monthly maintenance
Hosting, database, backup, support and continuous adjustments. Optional, and cancellable at any time.
Evolution
A new module is a new scope, quoted separately. Nothing is charged without being agreed first.
Prices are set case by case, after discovery. No project starts without a signed scope and price.
Frequently asked
What people ask before signing.
How long does it take?
It depends on the number of modules and the quality of the data that exists today. The timeline is set in the scope, split into stages, and every stage has a date.
Do I have to migrate everything at once?
No. The most common path is to start with the process that hurts most and bring the rest over later, as the team finds its rhythm.
Do you keep the data?
No. The data and the system belong to the client. Export is available at any time, with no formal request.
What if my team is not technical?
Most are not. Training is part of the delivery, and support runs over WhatsApp with whoever built the system, not through a ticket queue.
Do you only serve sport?
No. BSB Tech was born inside sport, but the core is management: people, contracts, deadlines, documents and results. That exists in any operation.
Do you build mobile apps?
The systems open in a browser and work on a phone. A published store app is a separate scope and has to be assessed case by case.
Next step
Ready for the first conversation?
Discovery costs nothing and commits you to nothing. Worst case, you leave with your process mapped.