Television station
Traditional broadcast to digital
A television station moved its whole operation to digital distribution. The broadcast it depends on ran throughout the migration.
We build software
that moves markets.
Founders with twenty-five years of production delivery, and a way of working that puts the risk on our side of the table. We agree the scope in writing before anyone writes code, deliver working software every two weeks, and send no invoice for a cycle we miss.
Software development has a trust problem.
For too long the choice has been to pay for hours and carry the risk yourself, or bend the business around software that was never built for it.
We think that is backwards. Software should fit the business, not the other way around.
At BUMM, the people you meet are the people who build. Senior engineers who understand not only how software should work, but what it has to do for the business.
Every two weeks we deliver something that works.
- Not progress reports.
- Not promises.
- Working software.
- AI makes us faster.
- Business understanding keeps us focused.
- Our engineers stay accountable.
If we miss what we committed to, we absorb the cost.
We do not sell development capacity. We take responsibility for the outcome.
The people who scope it build it.
The person who scoped your project runs it and stays on it. Your time goes to two points a cycle: what we plan, and what runs at the end of it.
One named owner, plus a second senior who reviews every change and could take the system over tomorrow. Two people always know it.
Two seniors on every engagement
A named owner plus a second senior who reviews every change. If one is ill or leaves, the other already knows your system.
Everything in the document
Scope, acceptance criteria and decision rights are agreed in writing before code, where you can hold us to them.
The work we turn down
Brand and campaign creative belongs to an agency. Round-the-clock operations is a separate engagement, and you hear that on the first call.
Work our founders led. Clients unnamed until they say otherwise.
Three engagements. In each one the operation had to keep running while it moved.
E-commerce platform
EUR 20,000 a month to nothing
A live e-commerce operation was paying around twenty thousand euros a month to licence its platform. It now runs on software the client owns outright, and the shop stayed open through the switch.
High-traffic sites
Millions of visits a month
Sites our founders built and still run serve millions of visits a month. The capacity was designed in at the start.
Founder-led work. Client names stay off this page until they release them. Referees from these engagements are available before you sign, and before you spend an hour on a call.
What we commit to. In writing, before you sign.
The questions buyers usually have to extract on a call, answered here.
- A change is yours. A defect is ours.
- Anything outside the agreed acceptance criteria is a change request, priced in writing before it starts. Anything that fails those criteria is a bug, and we fix it at our cost.
- Miss the date and the cycle is on us.
- When we fail to deliver what we committed to in a two-week cycle, we absorb that cycle. On a fixed-price Statement of Work the equivalent remedy is named in the contract before you sign.
- You own it in real time.
- Code, infrastructure and documentation sit in your accounts from the first day, well before final payment. We hold nothing back as leverage.
- The price before the signature.
- The number is agreed in writing before each Statement of Work is signed, and it moves afterwards only through a change you have approved.
- After acceptance, on retainer.
- If you want us to stay, ongoing work runs on a monthly retainer you can end at any point. If you would rather take it in-house, everything is already yours.
Three ways to work with us. Chosen by how much you hand over.
We take it over end to end, we build what you decide, or our engineers work inside your team. Each is bought as a fixed Statement of Work or as two-week cycles, and the price is in writing before you commit.
01
End-to-end delivery
You hand us the outcome. We own the product decisions, the delivery and the release, and your time goes to the cycle boundary.
Read more02
You lead, we build
You keep the product or project management. We are the senior engineering team that turns your decisions into working software.
Read more03
Alongside your team
Our engineers work inside your existing team: your board, your reviews, your standards. Senior capacity without a hiring cycle.
Read moreHow an engagement runs.
The same sequence for a two-person startup and a procurement department. Only the paperwork changes.
01
Conversation
A call with the engineers who would do the work. If we are the wrong team, you hear it on that call.
02
Scoping
Deliverables, acceptance criteria, milestones and who decides. Anything inside the criteria is ours; anything outside is a change, priced in writing before it starts.
03
Delivery
Two-week cycles, each ending in working software. A date at risk reaches you within one business day of us knowing it.
04
Handover
Code, infrastructure and documentation have been yours since day one. Leaving takes a notice period.
Agents write code. Engineers sign it.
Where AI sits between your requirement and your working system, and where a person still has to sign.
The tools and model providers that come near your code are named in writing before work starts, with the region they run in. A mode with no external model access is available on request to any client, whatever their sector.
01
Specification
A person writes the acceptance criteria before anything is built. Tests are checked against those criteria, never derived from the code that has to pass them.
02
Agent-assisted build
The repetitive work, the part that looks the same on every project, is done by AI agents under a senior engineer's direction.
03
Automated review
Every check is blocking. A failure stops the change, and clearing it takes a second engineer.
04
Human review
A named engineer reads every line and signs it off. Every generated line is read by a person before it reaches your system.
05
Release
The same checks every time, and the written specification is updated in the same change as the software.
Security reviewed every cycle.
Due diligence runs inside every two-week cycle. A problem found then costs a day; the same problem found a week before launch costs the date.
Settled at design, not before launch
Who can sign in, what they may reach, and how data is handled are decided when the system is designed.
A security finding stops the change
Dependency and licence checks run on every change, and a finding blocks it like any other failure.
The whole system, every cycle
Each cycle re-examines the entire system, including the parts nobody touched. Findings are fixed in that cycle.
A security regression is a defect
It is fixed as a defect, not filed in a backlog behind features.
We hold no ISO 27001, no SOC 2 and no third-party penetration-test report. If your procurement requires one, say so on the first call and you will get a straight answer about whether we can meet it.
Startups and enterprises buy different things.
Startups
Speed, and a partner who owns delivery.
Enterprises
Documented scope and named accountability.
- What you buy
- StartupsA senior team on a cadence, and a first release you can put in front of investors and users.
- EnterprisesA Statement of Work: deliverables, acceptance criteria, milestones and a fixed envelope, agreed before code.
- What it costs
- StartupsPer two-week cycle. Stop at any boundary.
- EnterprisesA fixed envelope agreed up front. A change is priced in writing and you approve it before it starts.
- When something slips
- StartupsYou hear it within one business day of us knowing, and we absorb the cost of a cycle we miss.
- EnterprisesYou hear it the same way. What falls out of a late milestone was agreed at scoping, and the remedy is written into the Statement of Work before you sign it.
- Who is accountable
- StartupsOne senior engineer across every cycle, with a second senior reviewing every change.
- EnterprisesA named technical lead from kickoff to acceptance, reviewed the same way.
- What you own
- StartupsEverything, from the first day. Code, infrastructure and documentation sit in your accounts.
- EnterprisesThe same, with the arrangement written into the Statement of Work for your procurement file.
—
Most engagements do both: sprints to find out what the system needs, then a Statement of Work once scope holds still.
A new company with twenty-five years behind it.
The four people who run BUMM have spent twenty-five years building and shipping production software, and they led all three engagements above. The person who scopes your work is one of them, and so is the person you escalate to.
- Twenty-five years of production systems, still on the tools.
- EU engineers, EU contracts and EU data protection on every engagement.
- No account manager between you and the people writing your code.
You can buy capacity by the day. Judgement arrives with the people who have already made the mistakes.
Vienna, Ljubljana, Trieste. One drive apart.
We work across three cities in two countries, inside one time zone and one legal market.
The farthest two are 350 km apart, so being in the room with you is a morning rather than a project. The contracting entity is the same wherever you are, and the law that governs your engagement is named in the Statement of Work before signature.
Vienna
Austria
Ljubljana
Slovenia
Trieste
Italy
Tell us what you're building. We'll tell you how we'd build it.
One call with the engineers who would do the work. We sign your NDA before you describe anything confidential, and if we are the wrong team you hear it in the first fifteen minutes.