Who we are
The studio is new. The people are not — our team has spent the last several years shipping production systems for clients in the United Kingdom, Canada, the United States, the UAE and Pakistan, across Laravel and Node platforms, Java microservices on Oracle, WordPress and Shopify builds, and data pipelines processing hundreds of gigabytes a day for a national mobile operator.
We started Compilux because most of that work arrived the same way: somebody had a system that had grown past what anyone could explain, and needed it turned back into something their own team could run. That is the whole business.
We are deliberately small. You talk to the person writing your code, scope and price are agreed before work starts, and every account is registered in your name from day one.
Approach
Four steps, in this order, every time.
The order matters, so we do not skip ahead. Most projects go wrong in step two, when nobody agreed what "done" meant.
-
01
Brief Week 0 · free
A call and a written summary of what you actually need — which is often not what you first asked for. You keep this document whether or not you hire us.
-
02
Scope Week 1
A fixed scope, a fixed price and a delivery date, itemised so you can cut anything you do not want. No hourly billing and no change-request games.
-
03
Build Weeks 2–8
You see working software every week, on a real URL, not a slide about progress. Anything off-course gets corrected while it is still cheap to correct.
-
04
Handover Final week
Code, accounts, documentation and a walkthrough recording, all in your name. You can keep us on support or run it yourself. Both are fine.
Our Values
Six commitments that cost you nothing to check.
You own everything
Repositories, servers, domains and third-party accounts are registered to you from day one. There is no version of this where leaving us is difficult.
Fixed price, fixed scope
You approve a number before work starts. If we estimate badly, that is our problem to absorb, not a change request we send you.
Senior people only
The person who scoped your project writes the code. Nothing gets quietly handed to a junior after you sign.
Written down, not remembered
Decisions, trade-offs and the reasons behind them are documented as we go, so the next developer — ours or yours — is not guessing.
We will say no
If the work is wrong for us, or you do not need it, we say so. A short honest answer is worth more than a long engagement that fails.
No surprises in the invoice
What we quoted is what you pay. Anything genuinely new is quoted separately and approved before it starts.
Testimonials
We would rather show you nothing than invent something.
No testimonials yet
Compilux is new, and we are not going to fill this page with quotes nobody said. As soon as a client puts their name to one, it appears here. Until then, judge us on the work in the portfolio and on the terms we put in writing.
See the work insteadStart with something small.
A first project we can both judge each other on beats a long pitch. Tell us what is broken.