About
A small studio that builds the unglamorous parts
Most of what we make is used by people at work, every day, to get something done. It has to be quick, obvious, and still make sense to whoever inherits it.
What we are, plainly
Maera Tech is a small team of developers. There are no account managers between you and the people writing your code, which means the person on your first call is the person who builds the thing.
We work on custom software rather than templates: the portal that replaced a shared inbox, the storefront that finally handles tax properly, the integration that stopped someone re-typing orders between two systems. It is rarely the sort of work that wins design awards. It is the sort that people notice the day it stops working.
Because the team is small, we take on fewer projects than we are asked to. That is deliberate. We would rather do four things properly in a quarter than twelve badly, and it is why we will sometimes tell you we are not the right fit.
At a glance
- Working since
- 2019
- Team
- Developers only, no layers
- Engagements
- Fixed price or retainer
- Code ownership
- Yours, in full
- Contracts
- NDA, MSA, and DPA
- Currencies
- USD · GBP · EUR · INR
How we work
Four things we hold to
Not values on a wall. These are the rules that decide what we do when a project gets difficult.
Say the number early
A quote that arrives after the work has started is not a quote. We would rather lose a project at the scoping stage than surprise you at the invoice.
Write it down
Anything that exists only in a conversation is lost within a week. Decisions, changes, and the reasons behind them go in writing the same day, where you can find them a year later.
Boring tools, on purpose
We choose the well-documented option over the interesting one. You should be able to hand our work to any competent developer without a translation layer.
Tell you when not to buy
Sometimes the honest answer is an off-the-shelf plugin, a different specialist, or nothing at all. Saying so costs us one project and earns the next three.
Fit
Who we are good for, and who we are not
Worth checking before either of us spends an hour on a call.
A good fit
- You have a specific problem, not just a budget
- Someone on your side can make decisions
- You want to own what gets built
- You would rather hear a hard no than a soft yes
Probably not us
- You need someone on site every day
- The scope has to stay open-ended
- Price is the only thing being compared
- You want a team that never pushes back
Next step
Meet the people who will do the work.
No account managers, no handover to a team you have not met. The person on your first call is the person writing your code.