Custom software development built around the way your business runs

Buy first when your process looks like the one the product was designed for. Salesforce and HubSpot handle a standard sales pipeline well, and Odoo covers a lot of ordinary accounting and stock work. If your team can adopt their way of working with light configuration, a subscription is cheaper and faster than a build.

Build when the process is how you compete, or when the workarounds cost more than the work. We often end up with a mix: keep the SaaS that fits, connect it through its API, and build only the part it cannot express. Our integration work covers that wiring.

• Per-seat pricing grows faster than the value your team gets from the seats
• Your approval or pricing rules need custom code inside the SaaS anyway
• Data you need sits across several tools and nobody trusts the combined report
• You need to own the system and host it where your data rules require

Every build starts from the data model: the records your business tracks, how they relate, and who may read or change each one. We write it in TypeScript and PostgreSQL so the types in the code and the tables in the database agree, and a whole class of bugs fails at build time instead of in front of a client.

Access control lives in the database as well as the interface. For a development agency we replaced four SaaS subscriptions and a master spreadsheet with one platform that runs deal to client to project to time to invoice to Stripe settlement, and Postgres row-level security decides which rows each user can see. Bollard, our own procurement and inventory product for multi-site operators, enforces its approval and three-way-match controls in the database across seven modules.

A rule enforced in the database holds even when someone writes a new screen, a script or a report later and forgets to check permissions.

Ask who owns the repository, what documentation you receive, and how often you will see working software. Ask how access rules are enforced and where the system will run. Clear answers to those questions tell you more than a portfolio page.

Our answers are fixed in the proposal. You own the code and every account it runs on. You see demos at the end of each short sprint. Security hardening and deployment are part of launch, and you speak to a founder rather than a sales team.

• Code in a repository under your organisation from day one
• Architecture, data model and admin documentation written for your team
• Scope, milestones, system design and pricing agreed before the build starts
• Handover and training so your staff can run and extend the system

Price follows the number of modules, the number of roles and approval paths, the systems you need to connect, and how much data must move across from spreadsheets or old tools. Discovery maps those, and a fixed quote with milestones follows it.

Rolling out an existing product is quicker than building from nothing. Bollard reaches its first live site in 14 days because the modules already exist. A custom system takes longer, and we usually ship the module that removes the most manual work first so your team uses real software early. After launch we include 30 days to 3+ months of support, and long-term maintenance is available.