Build and support
We build so that you can leave.
Custom software for the web, the phone and the desktop, integrations, and the modernisation of what somebody else left behind. The contract hands you the code and the rights to it. Every decision behind it is written down. The support runs against numbers published further down this page.
The ladder
Any of the five rungs is a place to begin.
Discovery sprintOne to two weeks · fixed price Before anything is built: the scope, a prototype, a plan and a quote, all of which you could take to somebody else.
- Conversations with the people who will use the thing
- A technical sketch and the decisions it forces
- A prototype you can handle rather than one we describe
- A plan and a price, stage by stage
- The risks, named one by one
What comes out is yours, even if you do not carry on with us.
First-version packageFixed scope · fixed price A product that runs, in weeks. What the price covers is settled in writing before anything starts, and so is what happens if the scope moves.
- A product that does one thing and does it well
- Release to the stores or onto your own infrastructure
- Training for the team that will take it over
- What is out of scope, in writing, so nothing surprises anyone
Where it starts: the discovery sprint, if the scope is not settled yet.
Full buildIn sprints Web, phone, desktop, integrations, and the road out of a system you inherited.
- Web applications and portals
- Phone applications, on both platforms
- Desktop applications and internal tools
- Systems joined together, and data moved between them
- A legacy system carried across in steps, without stopping the business
Over all of it: the code, the repository and the rights are yours from day one.
Support plansMonthly retainer Three tiers with published response times, and the numbers are further down this page rather than in an annex to a contract.
- Monitoring of the system and security updates
- A first reply to a defect inside the published response time
- A monthly budget of hours for changes, from the second tier up
- A named engineer and restore drills, on the third
The price follows the size of the system and the tier. We name it after half an hour of conversation.
Product partnerMonthly retainer The product keeps moving, with people who already know it, instead of a series of separate commissions.
- A reserved share of the month, known in advance
- Priorities put in order with you, every month
- Everything in the support plans is included
- Ends on notice, with no penalty
Who it is for: a product that will live for years, not a project with an end date.
Support
The numbers, published.
These are the times the studio answers in. They stand on the page so that you can hold them beside somebody else’s before you sign anything.
| The plan | Window | Critical | Major | Minor |
|---|---|---|---|---|
| Watch | Working days, 9 to 18 | within 8 working hours | within 2 working days | within 5 working days |
| Care | Working days, 9 to 18 | within 4 working hours | within 1 working day | within 3 working days |
| StandbyFor critical: every day, 8 to 22 | Working days, 9 to 18 | within 2 hours | within 4 working hours | within 2 working days |
They are not times to a fix. The clock runs only inside the plan’s window. After the first reply an update follows at every further interval of the same length, for as long as the problem is open. How long the fix itself takes depends on what broke, and is agreed case by case.
- Watch. We keep the system monitored and current on security. Fixes are billed by the hour.
- Care. On top of that, a monthly budget of hours for changes and priority over new commissions.
- Standby. On top of that, a named engineer who already knows your system, and two restore drills a year.
- Critical. The system is down, unusable for everyone, or the money has stopped moving.
- Major. An important function is broken. Work continues, badly.
- Minor. A defect that irritates, or a question waiting for an answer.
The craft
How the quality is held.
- A second pair of eyes on every change. Nothing reaches you that another person has not read.
- Automated tests before every release. When something breaks, we find out before you do.
- Security by default. Secrets do not live in the code, dependencies are updated on a schedule, and nobody holds a right they do not need.
- Built for the keyboard and the screen reader. Motion stops when the visitor’s system asks for less of it, and the colours give way to the ones a high-contrast system forces. This site is built that way, and so is everything we build for you.
- No third party rides along with the page. What a page of ours needs is loaded from your own address and from nowhere else, so nobody outside the agreement gets to watch your visitors. The page you are reading now is one of them.
- The environment comes up from a description. Not from one person’s memory, and not from their machine.
The ground
How the work is set up, and who you sign with.
- Choosing the stack. Usually the estate you already have decides it, and on a new build it is chosen for the people you will be able to hire afterwards.
- The cloud. A large provider, or your own machines when the data must not leave them. The choice is arithmetic against your real volume, and the arithmetic is written down where you can check it later.
- Where your code lives. In your accounts wherever you have them. In the studio’s only by written agreement, with the day it moves back to you named before the work starts.
- What becomes yours and what comes with a licence. Everything written for you is yours outright. The ready-made parts the work stands on keep the licences they came with, and those licences are listed in the handover before you accept it.
- Who you sign with. STUDIO KIRILOV EOOD, registered in Bulgaria as СТУДИО КИРИЛОВ ЕООД under company number 208911968. Bulgarian law governs the contract unless we agree on another jurisdiction inside the European Union.
- Confidentiality. Your own agreement can be in place before the first conversation, and the contact page says how fast that happens. What the studio learns about your business does not travel to another client, and no work of ours appears anywhere with your name on it unless you put it there.
Our own game is built under the same rules. It is also the one place where we are the client, which makes it the most honest test of how we work.
The beginning
Start with a discovery sprint.
Tell us what you need made and who it is for. A person answers. The answer is usually a list of questions, because questions cost less than a product built the wrong way.