Services
Software development
We build the internal tools and the integrations missing between your public site and the software your company already runs.
The problem we solve
Most of the companies we work with do not need another piece of software. They already have several: a CRM, an accounting package, sometimes a full ERP, each chosen on its own and none of them connected. What is missing shows up elsewhere — in the person who retypes every enquiry from the website into the CRM by hand, in the spreadsheet somebody keeps on the side because the official tool does not cover that part of the job, in the file nobody else knows how to update when that person is away. The work gets done, but it gets done by hand, and it leaves nothing behind that anyone can use.
We write the part that is missing between those tools, and nothing beyond it. For Cathena Group, an ERP integrator, that took the form of a webinar registration system wired directly into their Odoo CRM: a form filled in on the public site writes into the tool their teams were already using, with no retyping and no new account to learn. That is the scale we work at — a connection between two systems that ignore each other, an internal tool that replaces a shared spreadsheet, a business application for a company whose process fits no existing product. We are an agency, not a software publisher: when something off the shelf already does the job, we say so and help you put it in place rather than rebuild it.
What you receive
Written functional spec
The process as it runs today, screen by screen and case by case, with what the software will do and what it will not, signed off before the first line of code.
The internal tool, in service
An application your team reaches from a browser, with your own user accounts and access rights, running on hosting that belongs to you.
Integrations with the systems you already run
The connections that move information between your site, your CRM and your other tools — such as the webinar signup wired into Cathena Group's Odoo CRM — with a written list of what data travels in each direction.
Migration of your existing data
What lives in your spreadsheets and files moved into the new tool, duplicates removed, with a count of what was imported and what was not.
Documentation and a handover session
A short manual for the people who use the tool, a technical note for the next developer, and a recorded session your new hires can watch again.
The source code, in your name
The code repository and the access to the hosting and the database are handed over to you: if we stop working together, another developer can pick the project up.
How we work
01
Watch the process as it actually runs
We spend time with the people who do the work today, including the workarounds they invented to get through it. Those workarounds are what show where the software belongs; a spec written from the top of the company always misses them.
02
Take stock of what your tools can already do
Before deciding what to build, we look at what your existing software already exposes and what it will accept from outside. This step sets how much code there is to write — usually far less than expected.
03
Decide what will not be built
We cut the scope now, not halfway through, once we know what already exists. A tool that does three things properly gets into service; a tool that was meant to do everything is still in development a year later.
04
Put a first version into real use
We deliver the most-used part first, on your real data and with the people concerned, rather than a finished tool presented at the end. A demo does not surface the edge cases; a week of real use surfaces all of them.
05
Correct, document, hand over the keys
The edge cases from the previous step are handled, the documentation is written while the code is still fresh, then the repository and the access go to you. Put off until after launch, it never gets written.