Custom Development
Software built for the way you already work.
The product you bought covers most of the job. The rest is where your team loses its week: the export someone runs by hand every Friday, the two systems that disagree about the same customer, the spreadsheet nobody dares to touch. We build the software that closes that gap.
What we build
Four kinds of work, all of them finished.
- Web applications
- Customer portals, ordering and booking flows, and dashboards for the numbers your team actually decides on. Built for the browser first, so there is nothing to install and nothing to keep updated on anyone's machine.
- Integrations
- The connection between two systems you already pay for, built for your data model rather than a vendor's, with the retries, logging and reconciliation that make it trustworthy at three in the morning.
- Internal tools
- The small application that replaces the spreadsheet everyone is afraid to edit. It starts from that spreadsheet, keeps what works in it, and adds the validation, history and permissions it never had.
- Sites and content platforms
- Fast static sites in several languages, with build checks that refuse to publish a broken link, a missing translation or an unreadable colour. This site is one of them.
How we work
Small releases, real tests, no surprises.
-
Scope the smallest useful thing
We start with the version that is worth having on its own, and we write down what is out of it. A short list of what we are not building is the most useful thing a scope can contain.
-
Ship it in weeks
The first release goes to the people who will use it, early. What they do with it decides the next release more reliably than any plan written before they had it.
-
Every fix comes with a test
A bug is fixed by first writing a test that fails because of it, then making that test pass. The test stays, which is why the same bug does not come back.
-
Documented as it goes
Every release says what changed and what did not. When the project ends, your team inherits software it can read, not a black box with our phone number on it.
What we have shipped
Our own products are the portfolio.
We build our own products the way we would build yours, and they are public, so you can judge the work itself rather than a description of it.
Six Forge apps on the Atlassian Marketplace, each documented on our wiki. This website, in three languages, with build checks that stop a broken link, a missing translation or an unreadable colour from going live. And Kindelve, a browser game whose simulation gives the same answer on every device, and whose server proves a leaderboard score by replaying it.
From the blog
Notes on building software.
A backend for five dollars a month: when edge hosting is the right call
The default backend for a new product is a server, a managed database and a bill that starts in the tens of dollars. For many small products, edge functions with an edge database do the same job for a fraction of it. Our game's backend as a worked example, with the numbers, the constraints and when not to do it.
Cloud saves that never lose progress: merge by what a field means
One account on many devices means two devices will eventually be played offline and then sync. Last writer wins deletes progress; taking the maximum of everything duplicates currency. How Kindelve merges a save field by field, according to what each field means.
Build gates: how our website refuses to publish its own mistakes
This site ships in three languages from Markdown and TypeScript, and the mistakes that used to reach production now fail the build instead. The checks we run, from translation parity to accessibility in a real browser, and what they deliberately do not try to do.
Tell us what you are working around.
Describe the job your current tools leave undone, in English, Portuguese or Spanish. You will hear back from a person who builds software, not from a sales queue.