— Halifax, Nova Scotia
Custom software development in Halifax, scoped in writing.
Internal tools, web applications, integrations and AI features for Nova Scotia organisations that have outgrown spreadsheets and packaged products. The engineers who scope the work are the ones who build it.
The short answer
Custom software development means building an application around how one organisation works: an internal tool, a customer portal, an integration. SetKernel builds it for Halifax and Nova Scotia businesses that have outgrown spreadsheets or packaged tools. Work starts with a two-paragraph written brief, answered within one business day; a focused tool typically ships in three to six weeks.
— What we build
Software shaped to one business.
Most projects fall into one of these. If yours is staff retyping the same data into three systems, that is the brief.
- Internal tools: dashboards, admin panels and workflow apps for your own team
- Web applications with accounts, data and business rules, such as portals and booking systems
- Integrations between systems that should already talk: CRM to billing, store to fulfilment
- APIs that are documented and versioned for whoever consumes them
- AI features inside a product: document processing, retrieval over your own content
- Rescues of a legacy system whose vendor or author has gone
— How a project runs
Decisions written down before estimates.
A one-page memo fixes what success looks like. For longer builds, an architecture document comes before the scope is fixed: data flow, security, hosting, where AI is and is not used. Then two-week sprints, each closed with a demo and a changelog. Cutover follows a runbook with a rollback, behind a feature flag where possible, and we monitor for 14 days afterwards at our cost.
— Handover
You can run it without us.
The code lives in your repository and the credentials are yours from the start. Handover includes an operations handbook and a recorded walkthrough of every routine task: deploying, rotating secrets, running a migration, restoring from backup. Some clients take it from there. Others keep us on to operate it.
— Cost
What a quote depends on.
The number of systems to connect, and how well each one is documented. How much existing data has to be cleaned and moved. How many kinds of user there are and what each may see. Whether an old system must keep running during the changeover. The price is fixed in writing before work starts; if the scope changes, you hear about it in writing first.
— Where the data lives
Canadian data residency, decided up front.
PIPEDA does not forbid storing personal information outside Canada, but you stay accountable for it wherever it sits and must be open about it. Nova Scotia public bodies and their service providers face stricter rules under the province’s Personal Information International Disclosure Protection Act, and health custodians answer to PHIA. So the hosting region is a line in the architecture document, chosen before any code is written.
— Not the right fit
When buying is smarter than building.
If a packaged product does the job with tolerable workarounds, buy it; we will say so in the first reply. We also decline competitive RFPs, hourly staff augmentation, and discovery calls with no written brief.
— Questions
Before you write.
How much does custom software cost in Nova Scotia?
It depends on scope, so there is no rate card. You get a fixed price in writing before anything starts, based on the integrations, data and user roles involved. Asking costs nothing: send a brief.
How long does a custom software project take?
A focused internal tool or automation with few integrations can ship in three to six weeks. A full web application with accounts, a database and custom business logic typically takes eight to sixteen weeks. The timeline is set in the engagement memo.
Who owns the source code?
You do. The code sits in your repository, you hold the credentials, and any engineer you hire later can work on it. There is no per-seat pricing and no lock-in to us.
Can you take over software another developer built?
Yes. We inherit codebases, stabilise them first, and then move them forward. The first step is reading the code and the hosting setup, and telling you in writing what state it is in.
Can our data stay in Canada?
Yes, when the project calls for it. The hosting region and any outside services that touch personal information are chosen in the architecture document, and you approve that document before the build begins.
— Engage
A workaround that has become the system?
Tell us what you need built, what is in the way, and what done looks like. We reply in writing within one business day.