Shipped, and still running today.
Four platforms in production. Two of them we still operate.
- EzGrocery →
An e-commerce platform with live order tracking, payment and SMS gateways, and automated reporting across three Canadian provinces.
- Caterday →
A two-sided marketplace on Angular and Node.js, with admin control over parameters, clients, suppliers and reporting.
- Inverge Journals →
A publishing platform we built and still run — persistent identifiers, harvesting endpoints and an editorial workflow that works.
- Insightful Journals →
A second platform, deliberately isolated from the first, with its production line rebuilt to publish four times as often.
What we build it with.
Chosen per project, and for what your team can maintain afterwards.
Questions we get asked.
Can you replace a legacy system without downtime?
Usually, by running old and new in parallel and moving traffic across in stages instead of flipping a switch late on a Friday. It costs more in planning and far less in recovery. Where a hard cutover genuinely cannot be avoided, we rehearse it against production copies until the timings are boring.
What happens to our existing data?
It comes with you, and it is normally the longest part of the job. We profile the actual rows early rather than the schema documentation, because that is where the surprises live. Migration scripts are written to be re-runnable, so the real cutover is a repeat of something already done a dozen times.
Do you build SaaS products with multi-tenancy?
Yes. Whether tenants are separated by row, by schema or by database is an early architectural decision with consequences for cost, isolation and every compliance conversation you will later have — so it is decided deliberately and written down. Our post on building scalable SaaS covers the trade-offs.
Will we be able to maintain it ourselves?
That is the intent. Conventional framework choices over clever ones, tests that run in your CI, infrastructure defined as code, and documentation written for the engineer who joins after we have gone. The repositories and cloud accounts are yours throughout, not just at the end.
Can you work alongside our in-house developers?
Yes, and it is often the better arrangement. Team extension puts our engineers inside your process and your repositories; a dedicated team runs delivery while your people stay close to it. Both models are described on our services page.
How much does a web application cost?
Scope, integration count and how much of the requirement is already settled drive it — not a rate card. Our consultation page sets out the six factors that move the number most, and a call turns them into a range for your project.
Other services.
- Agentic Software Development →
Senior engineers directing autonomous agents that plan, write and test in parallel — with a named human accountable for every release.
- Salesforce Implementation →
Sales Cloud, Service Cloud and marketing automation configured around how your business really sells — with adoption as the deliverable.
- Software & UI/UX Design →
Solution, visual and interaction design handed over as a system engineers can build from — accessibility designed in, not audited later.