Software that has to work on Monday.
Booking flows, client portals, internal tools and business websites — built by the people who also run your DNS, your mail and your identity. There is no handover gap because there is no handover.
An agency ships the site and leaves. We are the ones still answering the phone in year three.
Most business software fails slowly rather than dramatically — a certificate expires, an integration silently stops, a developer moves on and nobody has the repository. Building inside the same operation that runs your infrastructure removes the seam where those failures live. The people who deploy it are the people who monitor it.
Systems, not brochures.
Marketing sites are part of it, but the work that pays for itself fastest is usually the unglamorous internal thing that removes an hour a day from somebody’s job.
| Type | Typical example | What it changes |
|---|---|---|
| 01Business website | Typical exampleMarketing site with real search performance and a form that reaches someone | What it changesEnquiries you can attribute, and a site that loads on a phone |
| 02Booking & intake | Typical exampleAppointment flow with reminders, wired into your calendar | What it changesFewer no-shows, and nobody transcribing voicemails |
| 03Client portal | Typical exampleSecure document exchange and status visibility for your customers | What it changesThe status-update phone calls stop |
| 04Internal tools | Typical exampleJob tracking, quoting, dispatch, timesheets — the spreadsheet that outgrew itself | What it changesOne version of the truth instead of four conflicting files |
| 05Automation | Typical exampleRemoving double entry between systems that were never introduced | What it changesHours a week back, and fewer transcription errors |
| 06Integrations | Typical exampleConnecting Microsoft 365, accounting and a line-of-business application | What it changesSystems that behave like one system |
If an off-the-shelf product already does what you need, we will tell you and help you configure it. Building something bespoke that already exists is how consultancies bill, not how businesses win.
Four reasons this belongs with your MSP.
Not a pitch against agencies — they are good at what they do. But operational software has different failure modes, and those failures land on infrastructure people.
See managed IT
Identity is already our day job
Half of any internal tool is who can sign in and what they can see. We are configuring Entra ID for you anyway, so single sign-on is a configuration decision rather than a project risk.
We host it where we can watch it
The application sits in the same estate as your DNS, mail and certificates — with the same monitoring, patching and backup regime. Nothing falls between two suppliers, because there is one.
We are still here in year three
The certificate that expires, the API a vendor deprecates, the dependency with a published vulnerability. Somebody has to own those, and an agency’s contract usually ended at launch.
One contract, one escalation path
When the booking system stops taking bookings on a Saturday, you call the same number you call for everything else — and reach someone who can see the server, the DNS and the code.
Five stages, fixed scope.
Discovery is paid and short, and its output is yours whether or not we build. That keeps the quote honest and stops anyone guessing at a number.
Scope
Sit with the people who will use it. Write down what it must do, and explicitly what it will not do in version one.
Prototype
Clickable, not a document. Cheaper to argue with a prototype than with working software.
Build
Short cycles with something to look at each week. Fixed scope; changes are quoted, not absorbed silently.
Deploy
Into your estate, with monitoring, backups and certificates configured before anyone uses it.
Operate
Support agreement or clean handover with the repository, documentation and deployment notes.
The fastest way to waste a budget is to specify everything anyone might ever want. We ship the smallest thing that removes the actual pain, watch it get used for a month, then decide what version two should be with evidence rather than opinion.
zero lineups.
Skip the line. Order from your phone.
Order ahead
Maplewood · Bank St
Order #214 confirmed
Ready for pickup · 8:40 AM
Paid $13.25 · VISA ····4242
Maplewood is a fictional shop shown for illustration; we design and build ordering sites like this for real Ottawa businesses.
The part most projects skip.
The site you are reading now runs on this arrangement. It is a fair sample of both the standard and the maintenance.
The ones people actually ask.
If yours isn’t here, ask it directly — you’ll get an answer from an engineer, not a form letter.
An MSP that builds software. The difference matters: an agency optimises for launch day, we optimise for year three, because we are the ones who will still be supporting it. It also means we do not hand you off to a hosting company when something breaks.
No. Plenty of build work comes from businesses who manage their own IT. It does tend to go better when we already know the environment, because half of any internal tool is authentication and data access.
Fixed price against a written scope, quoted after a short discovery. Small automations start low; a portal with integrations is a different conversation. We will not quote a number before we understand the data, and we will tell you when off-the-shelf software would be cheaper.
Usually. Most useful work is integration rather than replacement — connecting your accounting package to your job system so nobody keys the same thing twice. If a vendor has no API we will say so rather than promise a scraper that breaks quarterly.
You do, on final payment. It goes in a repository you have access to, with deployment documented, so another developer could pick it up. We do not build hostages.
Either a support agreement, or you take it and run. Both are fine and neither is a trap. If we host it, the same monitoring and backup regime that covers your servers covers the application.
Sometimes. We will look, and we will tell you honestly whether it is worth repairing or whether you are better off rebuilding. That answer has gone both ways.
Next
The site you are reading is the sample.
Tell us the process that is costing you an hour a day. We will tell you whether software fixes it, and roughly what that costs.