Launched is not finished

We run this on our own products

The automation we would run for you is committed in this repository rather than living in somebody's head — a test suite of 2,449 cases across 257 files, and an accessibility pass over every public route that fails on a single WCAG 2.1 AA violation. We will run it in front of you on the first call.

That is the whole case, and it is deliberately the only one on this page. There are no logos or testimonials here: evidence you can check is worth more than evidence you have to take on trust, so what you get instead is the system itself, on screen, on the first call.

What we can do instead is show you the work. On 1 August 2026 we found that our own CI had not run in months — every push and pull request gate was filtered to a branch this repository has never had, so the checks were passing by never executing, and one publish workflow had been rejected outright on every push since July. We found it, fixed it, and wrote down which of the remaining workflows we would not switch on without a decision from the owner. That is the job, and it is the exact failure mode a partnership exists to catch: not a dramatic outage, but a safety net that quietly stopped being one and would have gone on reporting success indefinitely.

We will walk you through all of it on the first call — the gate matrix, a real run, the deploy lane, and that fix — in the repository they run in.

The questions that decide it

Why is this so much cheaper than an agency?

Because the cost structure is different, not the engineering. A traditional agency price carries account management, bench time, and a project team that rotates — you are paying for the org chart as well as the work. We price the work. The stack is also one we run in production for our own products, so the scaffolding every project needs — accounts, payments, deployment, testing — is not rebuilt from zero at your expense. What is not different: who writes the code, and how carefully.

What happens if you become unavailable?

Continuity is designed in rather than promised. Source code, hosting, and the domain live in your accounts from day one, not ours — you can revoke our access this afternoon and carry on. Everything needed to run and deploy the project is configuration committed to your repository rather than knowledge in somebody's head: the build steps, the deploy lane, the tests and the monitoring are all reviewable, and runnable by any competent developer without us. Partnerships run month to month after the three-month minimum, either side can end with 30 days' notice, and ending one includes a written handover rather than a cliff. No vendor of any size can honestly guarantee availability, so the question worth asking all of them is what you are left holding if it stops. Here it is everything.

How does payment work?

Retainers are invoiced monthly in advance, on the same date each month, against a three-month minimum and rolling monthly after that. Fixed-scope builds are typically 50% to start and 50% on delivery, with larger builds split across milestones instead. Either way the exact structure is written into the scope document before any work begins.

I have never heard of you. What protects my deposit?

A fair question to ask anyone, and the honest answer is structural rather than contractual. The first payment buys a written scope and a working build in week one — so if week one does not arrive, you have paid for one week of work and you stop. That is the actual reason the cadence is weekly rather than monthly: your exposure never exceeds one week at any point in the project, because there is never more than a week between you and the next thing you can click. Deposits are invoiced against the scope document rather than against a promise, and if you would rather start smaller, we will scope the smallest useful piece of the project and do that one first.

What does the three-month minimum mean?

It means the first three months are committed, because taking over somebody else's codebase and getting genuinely useful in it takes longer than four weeks — the first month is largely learning your systems, and cancelling at that point leaves you worse off than before you started. After month three it runs month to month and you can end it with 30 days' notice. No annual lock-in and no auto-escalating rate.

What if a quiet month goes by and nothing breaks?

That is the outcome you are paying for, and it is a fair question to ask before signing. A partnership buys ownership and availability, not a ticket quota: dependencies and frameworks still move underneath you, security patches still land, and monitoring still needs somebody reading it. If genuinely quiet months repeat, the honest answer is to move you to the ad-hoc hourly rate rather than keep billing a partnership you have outgrown — we would rather lose the line item than have you resent it.

Do I need a project or a monthly partnership?

A project if the thing does not exist yet and has a defined finish line — a site, an MVP, a platform. A partnership if it already exists and the work is recurring: updates, security patches, and the next set of features. A project usually becomes a partnership at launch, which is the point at which the recurring work actually begins. If you are unsure, say so when you get in touch — a straight 'you do not need us monthly' is a normal outcome.

Who owns the code?

You do, outright, at handover — source and infrastructure in your own accounts. No license, no hosting lock-in, no per-seat fee afterwards.

Prices and terms on this page are informational and are fixed per engagement in a written scope. They are an invitation to start a conversation, not a binding offer — see the terms. Full rate card, including fixed-scope builds, on pricing, and the engineering standards we can be held to on standards.

Tell us what's not moving

Bring the thing that has been on your list longest and what it is costing you to leave it there. You leave with a straight answer on fit and a number — including “you do not need us monthly”, which is a normal outcome. Prefer email? arberrexha.dev@gmail.com.

We reply within one business day.