Custom software development & consulting

Software built
around your business.

A new product. Better internal tools. An application your team has outgrown. We help you decide what to build, then bring the engineering team to make it work.

A laptop showing code beside a stack of notebooks, lit by afternoon sun.

What we build

What’s standing between you and what’s next?

Start with the problem. We’ll help define the scope, choose the right approach and turn it into working software.

You have a product to launch.

Turn an idea into a useful first version. We help shape the product, design the experience and build the application around what your users actually need.

  • Product discovery
  • MVPs
  • Web & mobile applications

Your team needs better tools.

Replace the spreadsheet handoffs and disconnected systems that slow people down. Build internal software that fits how your business works.

  • Internal tools
  • Customer portals
  • System integrations

There’s a useful place for AI.

Find the repetitive work worth automating, then build AI into a real workflow, with clear checks, human review and a reason to use it.

  • AI integrations
  • Workflow automation
  • Prototypes

Your software needs to evolve.

Add capabilities, untangle technical problems or bring extra engineering capacity to an existing product. We can work alongside your team or take on a defined project.

  • Product development
  • Modernization
  • Ongoing engineering

What to expect

Three ways to engage.

Discovery

A short, fixed fee

Work out what’s worth building. You get a scope, an estimate and a timeline you can take to your team, whether or not we build it.

Defined project

A project fee

Quoted once the scope is agreed, with a timeline attached. You see working software early, not at the end.

Ongoing engineering

A monthly arrangement

A set number of days each month to keep building, fix what breaks and plan what comes next. Pause or stop with a month’s notice.

Quotes in Canadian dollars, before tax. We agree the number before any work starts.

The work

Software with
a job to do.

Two examples to show the kind of work we do: a client project and a product of our own. There’s more where these came from, so ask about projects closer to yours.

  • 5+projects delivered end to end
  • 20+clients served
  • 10+years building software
  • 3countries our clients work from
The CRM dashboard, showing client and proposal counts, total quoted value, average ticket, and this month's new clients and proposals.

Client project · Web app

A CRM that turns quotes into proposals.

The need
Arquiteto Gamer, an interior design studio in Brazil, needed a faster way to price projects and send proposals.
What we built
A web app for customers, services and packages that generates branded PDF proposals with timelines, revisions and payment terms.
Result
A proposal now takes two clicks, instead of assembling PDFs by hand.
Setbly’s home screen with recent workouts and a progress chart. Setbly’s exercise screen with personal bests and a progress chart.

Our own product · iPhone

Setbly, a simple workout tracker.

Why we built it
We wanted a workout tracker that stays out of the way, so we designed, built and published one ourselves. We maintain it on the App Store.
What it does
Build routines, log your sets and reps as you train, and see your progress over time.
Try it
Install it and judge the quality yourself. It takes two minutes.

How we build software together

Talk to the people
building it.

You bring the context. We bring hands-on engineering experience and a practical way to move the work forward.

Tell us what you’re working on
  1. Start with the problem.

    We talk through who will use the software, what needs to change and what constraints you’re working with. The first question is what’s worth building.

  2. Make the next step clear.

    Agree on the scope, priorities and price before the build. Start with the part that will teach us the most or make the biggest difference.

  3. Build, review, improve.

    See working software early, not at the end. Give feedback directly to the team, so decisions stay close to the people making them.

  4. Keep moving after launch.

    Hand over clear code and documentation that any developer can pick up, or keep building together as your product and business evolve.

Software project questions

Common
questions.

What kinds of projects are a good fit?

Custom applications, new software products, internal business tools, AI integrations and substantial improvements to existing software. Our focus is software that serves a business need, rather than small brochure websites or standalone landing pages.

How are engagements priced?

It depends on the work. Discovery is a short fixed-fee piece of work. A defined project is quoted as a project fee once the scope is agreed. Ongoing engineering is a monthly arrangement for a set number of days. Prices are in Canadian dollars, before tax, and we agree the number before any work starts.

How long does a project take?

It depends on the scope, so we give you a timeline with the quote. We start with the part that teaches us the most or makes the biggest difference, so you see working software early rather than at the end.

Do we need a detailed specification for a software project?

No. Start with the problem, who it affects and what you want to change. If you already have designs or a specification, bring them along.

Which technologies do you use?

We’re not tied to one stack. We choose what fits the product and the people who will maintain it, and if you already have a codebase we work in it. Either way you get clear code and documentation that another developer could pick up.

Who owns the code, and how do you handle our data?

You do. Code, designs and documentation are yours, kept in your own accounts and repositories wherever possible. We sign NDAs, build with sample or approved data, and keep production data in your systems.

Can you work with our existing team?

Yes. We can work alongside your team on an existing product or take on a defined piece of work. We’ll agree on responsibilities and how to collaborate at the start.

Let’s start with a conversation

Tell us what
you want to build.

Bring us the problem, the current software or the idea you want to explore. We’ll discuss scope, priorities and a sensible next step.