05 / Custom software / Toronto
When the tool you need does not exist yet.
Custom software is for the gaps. Sometimes the work does not fit any product, or the subscription you have almost works but forces a bad process. We build the narrow tool that fits, connect it to the systems you keep, and document it so your team is not stuck.
Discuss your projectThe friction
Sound familiar?
Teams bend their process to fit software that was built for someone else. They copy data between tools, keep a spreadsheet on the side, or pay for features nobody uses. The workaround becomes the process, and it breaks whenever the person who built it leaves.
A better way through
A useful change.
You get a focused tool that matches the work, with the parts that matter most built first. It connects to what you already run, and the code and notes are handed over so your team or another developer can pick it up later.
The scope
What the work can include.
Scope and prototype
The smallest useful version of the tool described in plain language, with the data it needs and the decisions it makes.
Working build
The application built in stages, so you can see and test progress before the whole thing is finished.
Connections
Links to the systems you keep, added only where access and stability are confirmed during scoping.
Code and notes
Source code, setup notes, and a short explanation of how the tool is structured, handed over at completion.
In your business
Different industries. Familiar friction.
Illustrative use cases. Access, suitability and delivery scope are agreed for each project.
Food and hospitality
A growing kitchen wants one place to plan prep and stock across two locations instead of two spreadsheets.
AGREED FOR YOUR PROJECTWe check who updates the data daily and how errors should be caught before building.
Education and training
A tutoring centre wants to track student progress and renewals without a generic CRM that does not fit.
AGREED FOR YOUR PROJECTWe keep personal student data handling within your rules, confirmed during scoping.
Construction and trades
A builder wants job photos, site notes, and change requests captured together and shared with clients.
AGREED FOR YOUR PROJECTWe confirm what clients should see and what stays internal before anything is shared.
The work, in order
From a clear brief to a considered handover.
01 /
Define the gap
We describe the job the tool must do and the smallest version worth building, before any code is written.
02 /
Build in stages
You see working pieces early and use them on real tasks, so problems surface while they are still cheap to fix.
03 /
Hand over
Code, notes, and setup steps are handed over, along with a walkthrough for whoever maintains it next.
Good questions
Before we start.
Should we build this or buy a product?
We check existing products first. Custom work is worth considering when an important workflow cannot fit an available tool or when a specific integration is missing. The assessment compares those options before recommending a build.
What does it cost to operate?
The proposal separates design and build, hosting and connected services, and ongoing maintenance. We estimate usage for the agreed scope and identify the assumptions that could change the cost.
What do we agree before development?
The scope covers the first feature set, access, dependencies, acceptance criteria and delivery schedule. Ownership, licence terms, documentation and handover access are also agreed in the proposal. Any required specialist certification must be verified before it becomes part of the scope.
What happens after handover?
Your team receives the documentation and access agreed in the proposal, including any third-party licence restrictions. Your team or another developer can maintain the work under those terms. If you want SparkX support, we separately agree what it covers, the fee and how changes are handled.
A useful next read
Setup is once. Usage and support are not.
Also worth a look