hello@mbranch.lv
Riga, Latvia
Services
Two people, so we are direct about what we take on, what we charge for it and what we will not do. Nothing below needs a discovery workshop to explain.
For a business that already works and has a process straining under its own weight. We agree the smallest version that is genuinely useful, build it, and put it in front of real users inside a couple of months. Then we keep changing it while you learn what it should have been.
Typical shape: eight to sixteen weeks to a first release, then a lighter arrangement while it settles.
Someone built it and then stopped. Before we agree to anything we read the code and produce a short document: what it does, what is fragile, what it would cost to keep, and what it would cost to replace. That document is useful to you even if you never hire us.
The audit is a fixed price and takes about a week. It is charged separately, so there is no pressure on us to recommend the bigger job.
One React Native codebase, both stores, and the offline behaviour designed in from the start rather than bolted on when the first complaint arrives. We handle store submission, review responses and the release process, because that is where small teams lose weeks.
A monthly arrangement covering updates, monitoring, backups that are actually restored on a schedule, and a budget of small changes. We only offer this for software we built or audited, because we will not promise uptime on code we do not understand.
How we charge
We have never found a pricing model that survives a project changing shape, so we keep it simple and tell you early when something has moved.
Audits, a first release with an agreed scope, a specific integration. You know the number before we start. If we underestimate, that is ours to absorb, and it has happened.
For ongoing work where the scope moves every fortnight. You buy a number of days a month, we report what went into them, and either side can end it with a month of notice.
Hourly billing, unpaid pitch work, or building a proposal deck to win a tender. We also do not take equity instead of payment, which has come up more than once.
Questions we get asked
For most projects of the size we take on, yes, and it is faster than it sounds because nothing waits on coordination. For a project that genuinely needs six people, we are the wrong studio and we will say so on the call rather than hiring to fit your budget.
Usually a few weeks out, sometimes longer. We do not start a project we cannot give proper attention to, so if the answer is April we will tell you it is April.
You do, from the first commit, in your own repository where possible. The handover includes infrastructure, accounts and documentation. There is nothing in our agreement that makes leaving us expensive.
Yes, mostly within the EU, and we invoice in euro from SIA FqvB with a Latvian VAT number. We are in EET, which overlaps with most of Europe comfortably and with the UK for the whole working day.
Usually. We read it properly, we ask for changes when something is unreasonable, and we do not sign anything that makes an individual personally liable for a company's software.
Next step
Bring the problem in whatever shape it is in. Half a spec, a spreadsheet that has outgrown itself, a codebase nobody wants to open. We will tell you what we would do first, and whether we are the right people to do it.
Cookies on this site
We use one cookie to remember this choice. That is all that runs unless you allow analytics, which would tell us which pages people actually read. Saying no changes nothing about how the site works for you. The detail is in our cookie policy.