How we work
Four phases, explicit deliverables, typical durations. No motivational PowerPoint, no mid-project surprises, no vendor lock-in. We start from the problem and end with a system in production that stays yours.
Understand before proposing. One week of questions beats a month of slides. We map the real problem, stakeholders, technical and regulatory constraints, budget. Out comes a plan built on your context, not a template.
- Technical document
- Proposed architecture
- Cost & time estimate
- Key mockups
- Risk plan
The how. System diagrams, data models, API contracts, navigable prototypes for critical flows. Every architectural decision documented and motivated. Design is where you pay the debt before you accrue it.
- System diagram
- Data model
- API specs (OpenAPI)
- Navigable prototype
- ADRs — decision records
Development in sprints. Weekly demos with the client, no surprises at acceptance. Hardware in lab, iterative integration, field testing before go-live. Software you haven't tested in the field doesn't work: we learned that at Gardaland.
- Client git repository
- CI/CD pipeline
- Weekly demos
- Automated & field tests
- Living documentation
Go-live isn't the end, it's where the system starts living. Monitoring, on-call on critical paths, monthly evolutions driven by real metrics. Twelve years of partnership with Gardaland say it works.
- Monitoring & alerting
- Measured SLA
- Evolution roadmap
- Monthly reports
- Knowledge transfer
What we do. What we don't.
Code to the client, always
Git repository in the client's name from commit zero. Documentation handed over. No vendor lock-in hidden in creative licensing.
Founders accessible
Zero intermediary account managers. The people who sell are the ones who design. Founders pick up the phone.
Boutique <30, not an agency
Small team, senior engineers. One tech lead per project. There's no anonymous "junior team" behind the scenes.
Honest estimates, no surprises
Detailed estimate after discovery. Scope changes renegotiated openly. Never the finger pointed at the client to justify overruns.
Test in the field, not just in lab
Hardware tested where it will live. Real-site pilot before go-live. Reality always has one more variable than the simulator.
We say "no"
If the problem isn't in our wheelhouse, we say so right away and refer elsewhere. Less revenue, more reputation.
Have a system to integrate?
2-6 weeks of discovery. No commitment beyond that. If the problem is ours we'll discuss next. If it isn't, we'll tell you.
Write us → info@brkt.it