IT services and software engineering
Meritbyte writes the software, runs the infrastructure underneath it, and does the search and campaign work that brings people to it. Six practices, one contract, one person you can call.
Services
Most clients hire us for one of them and end up using three. The practices share a codebase, a project manager and a single invoice, so nothing gets lost in the handover between them.
01
Custom platforms, internal tools, and the APIs that hold them together.
Most of this work is replacement work: a spreadsheet that quietly became a business process, an ERP module nobody is allowed to touch, a monolith that takes an hour to deploy. We write in TypeScript, Python, Go and .NET, and we hand over documentation your own developers can work from.
02
Assistants, search and automation built on your own data.
Retrieval over internal documents, extraction from PDFs and scans, classification and forecasting against your own history. We build the evaluation harness before the demo, because a model that is right eighty percent of the time is a support ticket generator. We will also tell you when a rules engine does the same job for a tenth of the cost.
03
Sites and web apps that load fast on a mid-range phone.
Next.js, WordPress or Shopify, chosen mostly by who has to edit the thing after we leave. Accessibility and Core Web Vitals are part of the build rather than a cleanup phase, and we test on real devices before launch, not just a throttled desktop tab.
04
Campaigns judged on pipeline, not impressions.
Paid search and social, email and lifecycle, and enough tracking to show which of them paid for itself. Ad accounts are opened in your name and stay with you if you stop working with us. Reporting goes to a dashboard you can open yourself, at any hour, without asking us for a PDF.
05
Fix the site first. Then write.
Crawl and index problems, site structure and page speed come before a single new article. After that, content built around queries with buying intent behind them. Rankings are reported next to revenue, and we do not buy links.
06
Deployments that are boring on purpose.
AWS, Azure and GCP, with Terraform for anything that would otherwise be clicked through a console. Pipelines that finish in under ten minutes, alerts that mean something at three in the morning, and a runbook your team can follow without calling us.
Automated suites, regression runs before every release, and load tests shaped like your actual traffic.
One project manager, a written update every week, and a backlog you can read without a meeting.
Code and infrastructure review, penetration testing, hardening, and an incident plan written before you need it.
Research, wireframes and prototypes, tested with people who resemble the ones who will use it.
Warehouses, pipelines and dashboards aimed at the questions leadership actually asks.
Devices, accounts, licences and a helpdesk your staff can reach on the first try.
How we work
After that we plan in two-week blocks, and you can stop at the end of any of them. Nobody does their best work inside a twelve-month contract signed before anyone has written a line of code.
01
A week, sometimes two. We read the code, talk to the people using it, and write down what is actually true rather than what the last vendor documented.
02
Architecture, milestones, price and the assumptions behind all three. The document is yours to keep whether or not you hire us.
03
Two-week blocks, a demo at the end of each one, and a staging URL you can open whenever you want to see where it stands.
04
Monitoring, patching and a support agreement with response times written into it. Most clients stay on this part for years.
A defined outcome with a fixed price on the first milestone.
A set number of days each month for ongoing work and support.
Our engineers in your standups, reporting to your own leads.
About
We are a small team of engineers, designers and marketers. There is no account layer between you and the work: the person in the kickoff call is the one writing the code, and they stay on the project until it ships.
We take on a limited number of projects at a time, so occasionally the honest answer is no, or not until March. When that is the case we say so at the start, rather than taking a deposit and putting you in a queue.
Everything we build is handed over with documentation, repository access and credentials in your own name. If you decide to take it in-house or move to another firm, you can, and nothing breaks when you do.
Contact
Write a few lines about what you have now, what you want instead, and when you need it. If there is a budget range, include it. It changes the shape of what we propose more than anything else you can tell us.
hello@meritbyte.com