You already know what we build.This is where it lives now.
Launch is the hub we built to hold the applications we make for you. Sign-in, your staff directory, notifications and payments are written once and shared, so everything after the first application is smaller, faster and safer to add.
Why we built it
The same six problems, on every project
We kept solving these one at a time, for one customer at a time, and charging for the same work twice.
The old rule
Good, cheap, fast. Pick three.
Everyone has heard the version where you only get two. It was true when every application started from an empty folder and most of the budget went into plumbing somebody had already built, somewhere else, for somebody else.
Good
Not the corner you drop
Sign-in, permissions, notifications and payments are written once, tested hard, and already carrying five applications every day. You inherit that on day one.
Fast
Days, not quarters
A catalogue application gets fitted to how you work. A custom one starts on components that are already finished, so the build is only the part that is yours.
Cheap
You pay for your part
The plumbing was paid for once, by us. Your fee covers the workflow nobody else has, not a fifth rebuild of the things everybody has.
Nobody repealed the rule. We stopped rebuilding the same four things on every project, and that is what took the third corner off the table.
The hub
One hub. Every application.
The hard parts are written once, tested hard, and shared by everything on top. That is what makes your second application cost a fraction of the first.
The catalogue
What is already in there
The first five run our own business every day. We are not asking you to be the test.
Time tracking
Hours against jobs, approvals, payroll export
Live
Documentation hub
Policies and procedures, replacing the shared drive
Live
Learning centre
Onboarding, certifications and refreshers, with a record
Live
Employee directory
One list of people and roles, used by everything else
Live
Expense tracking
Claims, receipts, approvals, coding to accounts
Live
Permits and licensing
Applications, fees, inspections, renewals
In the catalogue
Service requests
Intake, routing, status and closure
In the catalogue
Built for you
Your workflow becomes an application, then joins the catalogue
Scoped together
Shared components
The four places custom software goes wrong
Written once, tested hard, inherited by every application in the hub. These are also the four places a breach starts, so reusing them is a security decision before it is an economic one.
Authentication
One sign-in everywhere. Multi-factor, lockout and session rules set once and applied to everything.
Identity and permissions
One directory of people and roles. Someone changes job and their access changes everywhere at once.
Notifications
Email, text and in-app, with a single record of what was sent, to whom, and when.
Payments
Other companies have perfected payments. We connect to them in a safe and secure way, extendable to every application in the hub.
Every one of these is work you have already paid somebody to do at least once. In the hub it is done, and it stays done.
How it works
Four steps, and you can watch all of them
Step 1
Scope
We sit with the people who do the work and write down what actually happens, including the parts nobody documented. Or we scan the existing system or process and verify rather than gather.
Step 2
Build
Work runs on a board you can watch. Agents draft, security and architecture agents review, and a person signs off at the marked limit.
Step 3
Deploy
It lands in your hub already wired to the sign-in, the directory and the notifications sitting there.
Step 4
Keep
Your instance and your data. Hosting is a monthly fee, not a licence that holds the software hostage.
Where we let the tools run, and where we don't
The tools move fast up to a marked limit. Past it, a person signs.
We use modern tooling to help with a great deal of this software. What matters is where the limit is drawn and who is accountable past it. Ours is written down before work starts, and it is tiered by how much damage a mistake could do.
Tier 1
Runs free
Layout, copy, reports, internal tooling. Reviewed, not gated.
Tier 2
Review before merge
Business logic and integrations, anything a daily workflow depends on.
Tier 3
Named signature
Sign-in, permissions, personal data, money movement. A person signs, by name.
Tier 4
Written by a person
Anything an auditor would ask about. The agent assists; it does not author.
This is published, not claimed. You are welcome to hold us to it, and to ask any other vendor for theirs.
Why the next one costs less
Built once for someone. Cheaper for everyone after.
When we build something specific for you, it can become a catalogue application. You get a lower price for allowing it, and the next customer gets it faster.
Step 1
Scoped
Priced against your workflow, not a licence tier.
Step 2
Built
On the shared components, so the risky parts are already done.
Step 3
Generalised
The specifics come out, the shape goes into the catalogue.
Step 4
Cheaper next
The following customer pays a catalogue price, not a build price.
✓You pay for your build, not for the plumbing that came before it
✓Catalogue applications deploy in days, because the hard parts are written and tested
The public side
Give your people answers, not another login.
The same hub that runs your staff applications gives your customers or residents one account for everything you offer, under your name rather than ours.
See where things stand
Requests, invoices and their status, current rather than as of last month's report.
Do it without phoning
Apply, upload, pay and track outside office hours, which is when most people have time.
One account, not six
One sign-in across every service you offer, instead of a separate account per system.
Time your front desk spends on status calls is the cleanest thing to measure after go-live. Count it for a week before we start.
Where it runs
Your instance, in Canada, yours to leave with
Single-tenant means your data sits in your own instance rather than in a shared database with everyone else's. That is a deliberate choice and it costs us more.
Your own instance
Not a row in a multi-tenant database. Your data can be exported whole, at any time, without asking.
Hosted in Canada
Canadian data centres, with no cross-border transfer needed for ordinary day-to-day operation.
A way out
If you ever leave, you take the data and the application. We would rather earn the renewal.
Hosting region and residency commitments are set per engagement and written into the agreement rather than assumed.
What changes
After the first application is live
Each application you add makes the others more useful, because they finally share the same people, the same permissions and the same record of what happened.
What it costs
A build fee, then hosting. No seats.
Shape of the model, not a quote. Figures are set per engagement, the same way we have always priced your work.
Fastest
Catalogue application
It already exists. We fit it to how you work, load your people, and it is in use.
Fixed build fee, then monthly hosting
Most common
Built for you
Your workflow becomes an application. Allow it into the catalogue and your build fee drops.
Scoped build fee, then monthly hosting
Ongoing
Hosting
Covers the instance, backups, updates and the shared components. Per instance, not per person.
Monthly, cancellable
●No per-seat licence, ever
●Portfolio clause lowers your build fee
●Your data exportable at any time
Getting started
One application, live in a fraction of the usual time
Not a platform decision. One workflow, scoped and priced, with something working you can put in front of your staff.
Step 1
Walkthrough
We watch how the work is done now and write down where it breaks. No slides.
Step 2
Scope
One application chosen, priced and put on the board, with the risk tier set per feature.
Step 3
Build
Built against that tiering. You see it working before it is finished.
Step 4
Live
Your instance, your people loaded, your first application in real use.
Pick one process that could be more efficient.
One workflow, scoped and priced, with a working version your staff can try. That is a far smaller decision than choosing a platform, and you already know how we work.
jeff.peters@dev-pro.ca