Custom Software and Client Portals
Some problems do not have an off-the-shelf answer, and forcing one costs more over five years than building the right thing did. We build the portal, dashboard, or internal tool your business actually needs, then host and maintain it on a licence so it keeps working long after launch day.
We Build It. Then We Run It.
Most custom software dies about six months after handover. Not because it was built badly, but because the developer moved on, nobody left knows how to deploy a fix, and the dependency warnings pile up until upgrading is its own project. Our model is build then licence: you pay for the build, then an ongoing licence covering hosting, monitoring, patching, and support from the people who wrote it.
Built
For Your Actual Workflow
Hosted
Monitored and Patched
Boring
Mainstream Tech, No Lock-In
Direct
Support From the Builders
What We Build
The Software That Does Not Come in a Box
If an off-the-shelf product fits your problem, we will tell you to buy it. These are the cases where one does not.
Client and Customer Portals
A logged-in space for the people you serve: documents, approvals, progress, and reporting, on your domain and in your branding. The thing that stops a client emailing to ask where something is at.
Booking and Intake Systems
Forms that feed something real, with conditional logic, routing, reminders, and a back end your team can actually administer without calling a developer to change a dropdown.
Reporting Dashboards
Live numbers pulled from the platforms you already use, in one view, with the definitions written down so two people reading the same figure agree on what it means. No per-seat business intelligence licence.
Internal Tools
The job your team currently does in a shared spreadsheet with colour-coded tabs and one tab nobody is allowed to touch. Built properly, with permissions, validation, and an audit trail of who changed what.
Integrations and APIs
Connecting your software to the systems around it, including the vendors with undocumented APIs and the ones where the integration is technically a nightly CSV. We have done both.
Hosting, Monitoring and Support
Uptime monitoring, error alerting, security patching, and backups, handled as part of the licence rather than remembered occasionally. Support comes from the people who wrote the code, not a ticket queue.
Why Stance
A Marketing Agency That Ships Software
We run our own client platform, our own reporting pipelines, and our own billing automation in production. That is unusual for an agency, and it is the reason we can build the thing rather than brief a third party and manage the gap between what you asked for and what turns up.
It also means we understand what the software is for. A booking system is not a technical artefact, it is the last step of a funnel we probably also built. Most development shops have never had to care whether the form converts.
Mainstream stack, no proprietary framework lock-in
Hosted, monitored, patched, and backed up under the licence
Support direct from the people who wrote the code
Data residency agreed before the build, not retrofitted
Ownership and exit terms agreed in writing before we start
Documented and version-controlled from the first commit
Software Is Usually the Last Piece
A portal is worth building once there is something to put in it. Most of our software work grows out of automation and reporting that has outgrown the tools it started in, for clients whose marketing we already run.
Frequently Asked Questions
Custom Software FAQs
Outgrown the Spreadsheet?
Book a discovery call. Tell us what the workaround currently looks like and we will tell you whether it is worth building, whether something off the shelf already does it, and what the build would involve.