hello@mbranch.lv
Riga, Latvia
Riga, Latvia / Two developers
mbranch is a two person studio. Emils leads the build, Georgiy takes the groundwork and reviews everything that goes out. We take on a handful of projects a year, which is a limit we picked on purpose: the person who wrote your code is the person who answers when it breaks.
What we do
If your project is not one of these, we would rather say so on the first call than three weeks into an invoice.
You have a business that works and a process that has stopped scaling. We build the first real version, put it in front of actual users, and keep changing it while you find out what it needs to be. The first version is deliberately small.
A contractor stopped replying. An in house developer moved on. We read what is there, write down what it actually does rather than what the documentation claims, and give you a plan with honest numbers before we change a line.
Built once in React Native, shipped to both stores, with the offline behaviour thought through early instead of patched in later. We handle the store submissions too, because that part goes wrong quietly.
Dependencies age, certificates expire, and tax rules change in January. For software we built, we keep a small monthly arrangement so that the first you hear about a problem is us telling you it has been fixed.
Selected work
Most of what we build sits behind a login and a signed agreement. These two we can talk about openly, so they are the ones on this page.
Live scoring, course maps and handicap tracking for players on the course, with a back office the club actually runs the season from. Built for a signal that drops behind the tree line.
Read the case notes
A planning tool for a team that had outgrown a shared spreadsheet and hated every product they trialled. Boards, a real schedule, and workload you can see before you promise a date.
Read the case notes
Clients
Every quote below is from someone who worked with us directly, and each one has approved the wording.
“Placeholder review. Replace this with a real quote before the section is published.”
“Placeholder review. Replace this with a real quote before the section is published.”
“Placeholder review. Replace this with a real quote before the section is published.”
Worked with
How a project runs
Nothing here is unusual. It is written down so you can hold us to it.
Thirty minutes to understand the problem, then a document from us: what we would build first, what we would leave out, what it costs and how long it takes. If the scope is wrong you find out while it is still a document.
Not a prototype and not a slide. One narrow path through the product, deployed somewhere you can open it on your phone. It is usually ugly. It is also the point at which most assumptions get corrected.
Fortnightly, with a short written note on what changed, what we got wrong and what is next. You can redirect the work at any of those points without renegotiating anything.
Repository, infrastructure, accounts and a document that explains the parts a new developer would get wrong. We would like to keep working with you. You should not be stuck with us to keep the thing running.
Who you get
There is no bench and no team we scale up from. When you hire mbranch you get the two people below, which is why we are careful about how much we take on.
Lead Developer
Owns the architecture and writes the code that touches money, sessions and anything you cannot afford to lose twice. If you book a call, you are talking to him.
Junior Developer
Interface work, test coverage and the unglamorous parts of a release that decide how Monday morning goes. He reviews every pull request Emils opens, which is an arrangement we both wanted.
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.