// about · cat README.md
The studio that stays
after the launch party
Ulogon exists because too much software gets built by people who will never have to live with it. We design, build and run systems, and that last word changes everything about the first two.
// the story
Why we work this way
Every engineer here has inherited a system with no documentation, no tests and no one left to ask. That experience shaped the studio. We write software as if we'll be the ones maintaining it, because usually we are.
We keep the team senior and small on purpose. The person who scopes your project writes the code, and the person who writes the code carries the pager. That loop keeps everyone honest in a way no process document can.
Clients stay with us for years, and the reason is unexciting: the software keeps working, the invoices match the quotes, and when something breaks at 3am, it's usually fixed before the morning stand-up.
// operating principles
Rules we don't break
Fixed prices, honest scopes
We quote after we understand the problem, then hold the price. Changes are re-quoted in the open.
Nothing ships unreviewed
A second engineer reads every change. Boring, and the reason our incident log is short.
You own your code and data
Full repository access from day one. Leaving us is easy, which is why nobody has to.
Plain English, always
If we can't explain a technical decision to you in one paragraph, we don't understand it well enough to make it.
// who we work with
A good fit, honestly stated
Established businesses
You have systems that run the company and they've outgrown the tools they started on. We modernise without stopping the business to do it.
Funded founders
You need an MVP that can survive real customers and a technical partner who tells you when you're about to waste money.
Agencies and consultancies
You sell the vision and need engineering that delivers it. We work white-label or side-by-side with your team.