Most case studies brag about what a team built. This one is about what we built, and what we chose to walk away from.
BrilliantHost was a VPS hosting product we built, launched, and scaled under the traztech brand. In under three months it hit 250 paying customers and $13K MRR. It was profitable. It was growing. And we shut it down on purpose.
If you are a founder or CTO trying to figure out whether a team can actually ship, and whether they have the discipline to make hard calls, that is the story worth telling.
What we built
BrilliantHost was VPS hosting for businesses and individuals. Not a reseller play. Not a thin wrapper over someone else's cloud. We built and managed our own infrastructure: physical servers, network, the whole stack.
Everything around it was ours too:
- Product development and the customer-facing platform
- Provisioning, monitoring, and operations
- Billing and account management
- Marketing and sales
- Customer support
The traztech team, small, senior, and tightly coordinated, owned every layer of it. Our founder led the build, and we ran it the way we run client engagements: end-to-end, no hand-offs, no excuses.
The results
- 250 customers acquired
- $13K MRR at peak
- Under 3 months from launch to that number
Three months is the part that matters. Going from a blank page to a real product with real customers paying real money, on owned infrastructure, in a quarter is not a marketing exercise. It requires the product, the platform, the billing, the support workflow, and the go-to-market motion all working at the same time. That is what a traztech team looks like when it executes.
Why we killed it
BrilliantHost was working. The numbers were trending the right way. The unit economics made sense. There was a clear path to keep growing.
We shut it down anyway.
traztech's center of gravity was moving, and has now firmly settled, into consulting, fractional leadership, and security: fractional CTO, CISO, DevOps, security engineering, and operations. That is where we create the most value, and where the most interesting work is.
Hosting is a different business. It demands round-the-clock infrastructure attention, support load that scales with customer count, and a margin profile that wants you to chase volume. Every hour we spent keeping BrilliantHost healthy was an hour we were not spending on higher-leverage work for startups that needed a security leader, a fractional CTO, or a serious operations partner.
The honest read was simple. BrilliantHost was a good business that was holding the team back from a better one. So we made the call.
This is the part most teams get wrong. Profitable does not mean strategic. Growing does not mean aligned. The willingness to kill something that is working, because it is pulling you off the path you actually want to be on, is one of the hardest disciplines in operating a company. It is also one of the most important.
How we shut it down
We had options. We could have sold the customer base. We could have let it slowly decay while we focused on other things. We could have hand-waved through the offboarding.
We did none of that.
Instead, we worked directly with all 250 customers on migration and offboarding. Every account got a real plan. Every transition was supported. Nobody got stranded, and nobody got a generic shutdown email and a 30-day countdown.
Winding a product down well is a craft of its own. It is slower than walking away. It costs more. It generates exactly zero new revenue. We did it that way because the people who trusted us with their infrastructure deserved a clean exit, and because how you end something says more about your team than how you start it.
What this means if you are hiring us
The BrilliantHost story is the short version of how we think and how we operate:
- We build fast. Zero to 250 paying customers and $13K MRR in under three months, on infrastructure we built ourselves.
- We think long-term. We will tell you to kill a product, sunset a system, or change direction when the data says so, even when it is uncomfortable.
- We do right by people. Customers, teams, and stakeholders get treated like they matter, on the way in and on the way out.
That is the same posture we bring to client work: fractional CTO, CISO, DevOps, security, and operations engagements with startups that need someone serious in the room.
If you are building something and you want a team that ships hard, thinks clearly, and is not afraid of the hard calls, book a strategy call.