Software built around how your business actually works.
Off-the-shelf tools fit until they don’t. We design, build, and run custom applications: portals, ordering systems, internal tools, and the connections between them. One accountable team, from the first workflow session to production and beyond.
- 1 Map the workflowA working session on what happens today, and where it breaks.
- 2 Build in stagesWorking software you can react to, with no six-month silence.
- 3 We run it afterMonitoring, updates, and incident response. A named owner.
Launch is the midpoint, not the finish line.
You’ll know it when you see it.
The spreadsheet that runs the company
Orders, schedules, or pricing live in a file three people edit and one person understands. Every hire makes it worse.
Systems that do not talk
The website, the accounting tool, and the warehouse each hold their own version of the truth. Someone retypes data between them every day.
The tool you have outgrown
The off-the-shelf app fit at 10 people. At 40, your team works around it more than in it.
The system nobody will touch
It still works, the person who built it is gone, and every change is a gamble.
None of these are software problems at first. They’re Tuesday. Then one breaks during your busiest week.
Built for the workflow you already have.
Customer and partner portals
Order status, documents, approvals, self-service. Clients stop emailing for updates because the answer is in front of them.
Ordering and workflow applications
From quote to production to delivery, modeled the way your operation actually flows, including the exceptions.
Internal operational tools
Scheduling, reporting, field apps, dashboards. The unglamorous software that saves an hour per person per day.
Add AI where judgment is involved →Mobile applications
iOS and Android apps for teams in the field, built on the same system of record as the office.
SaaS and subscription products
Productizing what you know: billing, accounts, and infrastructure included. We run six of our own, so we build yours like we will be operating it. Because we will.
Legacy-system modernization
We keep the old system alive while new rails go in underneath. No big-bang rewrite, no frozen business.
See how we connect systems →Understand first. Build second. Run it after.
Discovery and architecture
We map the workflow, the users, the systems involved, and where things actually break. You get a written recommendation and a phased plan, whether or not we build it.
Deliverable: a plan you can take anywhereBuild in stages
Staging environments, acceptance criteria, and working software you can react to. No six-month silence followed by a reveal.
Deliverable: working software, every stageOperate and improve
Monitoring, updates, incident response, and a named owner. The same operations discipline we are known for on WordPress and Odoo, applied to what we built for you.
Deliverable: a named owner, on callSystems that are running right now.
Guard-patrol reporting, in the field and in the office
A web application plus iOS and Android apps for Empire Security Services. Officers file incident and patrol reports from their phones, and supervisors get formatted PDF reports generated automatically. Built by Parameter and supported since.
Online orders that land straight in production
For a national engraved-stationery manufacturer: an ERP and storefront platform where online orders flow directly into production, including a custom document-personalization pipeline.
New rails under a system too critical to replace
For a corporate print company: a ColdFusion and Java order system kept in production while its shipping-rate integration moved to modern APIs underneath. The old system stayed up. The business never stopped.
Six products we designed, built, and operate
PreArrive, Letterhead Lab, Stackfill, SignedShoot, BeamHello, and Frontpagely: SaaS products Parameter runs end to end on Cloudflare, with payments, authentication, and rendering pipelines. We build client software the way we build our own, because we operate both.
The difference is who owns it afterward.
An account manager relaying messages to a team you never meet.
Launch day is goodbye day. Bugs after that are a new invoice.
Custom code proposed for everything, because that is what they sell.
One accountable owner. The person you talk to is the person building it.
We operate what we build. Monitoring, updates, and incident response come from the same team.
Platform-honest. If WordPress, Odoo, or an off-the-shelf tool solves it, we will say so and build the smaller thing.
Straight answers.
What does a typical project look like?
It starts with a working session on the workflow, not a proposal. We map what happens today, where it breaks, and who touches it. You get a written recommendation and a phased plan, then we build in stages against acceptance criteria you can see and react to.
Do you take over systems someone else built?
Yes, and that is most of what we do. Inherited applications, half-finished builds, and systems whose original developer is long gone. We start by getting it stable and documented, then improve from there.
What stack do you use?
Web-standard TypeScript and JavaScript applications on Cloudflare, PHP where the existing estate calls for it, and native-wrapper mobile apps for iOS and Android. We choose boring, operable technology on purpose, because we are the ones who have to run it at 2am.
Do you build mobile apps?
Yes, for iOS and Android, built on the same system of record as the web side so the field and the office are never looking at different data. Our guard-patrol reporting platform works exactly this way.
What happens after launch?
We operate it. Monitoring, updates, incident response, and a named owner who knows the system. Launch is the midpoint of the relationship, not the end of it.
Do we own the code?
Yes, for bespoke work we build for you. Ownership and licensing are written plainly into every proposal before work starts, so there is nothing to discover later.
Tell us what the spreadsheet does.
Thirty minutes, no pitch deck. Walk us through the workflow and we’ll tell you what we’d build, what we wouldn’t, and what we’d do first.
Book a call