Services · Software Development

Custom Software Development

Software built around the way your business runs, so you’re not bending the business to fit someone else’s product. I’m the only engineer on it, from the first conversation until it’s running in production.

A laptop on a drafting table showing a simple business application, beside the paper form and the printed spreadsheet it replaces.
The app on the left replaces the paper form and the spreadsheet on the right.

The promise

Every custom project starts with a 1-week discovery for $4,500 CAD, credited in full against the build. If it turns out the system wouldn’t get used, I’ll tell you, and you’ve spent the discovery fee instead of the cost of a build.

I don’t give a fixed price for custom software before I’ve watched the work. Any number before that is padded or a guess. So the first week isn’t spent building: I follow one real piece of work through your business and write down what I find. When internal software fails, it’s usually because people quietly go back to the old spreadsheet. A week is a cheap way to catch that before you pay for a build.

How a project runs

  1. 00
    Discovery 1 week · $4,500 CAD, credited in full

    I follow one piece of work from start to finish: where it comes in, who touches it, what gets typed in twice, and which spreadsheet is the real one. If you decide not to build anything, you still keep the systems map.

  2. 01
    The scope, in writing Before anything is built

    The systems map, a written scope, and a fixed price for whatever you decide to build. This is where a rough range turns into a real number, because by now I’ve seen the work.

  3. 02
    Built in phases Weeks per phase

    You see a working demo every week, so if a week goes nowhere, you know that week. I write each decision down, with the reasoning, the day I make it. If the scope changes, you get a price for the change before I build it, so nothing extra turns up on an invoice. You pay phase by phase, for work you’ve already seen running.

  4. 03
    Handover Yours to keep

    The repository, the documentation and the running system. The infrastructure moves to your own accounts, or stays on mine under the run plan, whichever you chose. If another engineer takes over in 2 years, that’s everything they’ll need.

What you get

  • A finished systemDeployed, monitored, backed up, and documented well enough that another engineer could take it over.
  • The code and the dataYour repository and your data, from the first commit. You’re never licensing something I own. On the run plan the system runs on my infrastructure, or in your own cloud account if you’d prefer. Either way, you can take it with you.
  • A data model that matches the businessIncluding the exceptions: the client billed differently, the job that skips a step, the field only one department fills in. Off-the-shelf products make you work around those.
  • The integrations it has to work withYour accounting, your email, the spreadsheet nobody will give up. Each one connected properly, with a plan for when one of them goes down.
jobs.xlsx 1042 booked jobs (2).xlsx 1042 done jobs-final.xlsx 1042 booked Inbox Bill 1043 monthly Jobs JobStatusBilling 1042doneper-job 1043booked monthly OfficeField crewAccounts jobs.xlsx 1042 booked jobs (2).xlsx 1042 done jobs-final.xlsx 1042 booked Inbox Bill 1043 monthly Jobs JobStatusBilling 1042doneper-job 1043booked monthly OfficeField crewAccounts
Three copies of the jobs spreadsheet and an inbox, brought into one table. The job they disagreed about becomes one record, the monthly billing from the email gets its own field, and everyone who kept a copy reads the same row.

Pricing

Fixed prices for the common jobs, and a quote after discovery for anything bigger. Prices in CAD, plus GST.

  • 01
    Discovery

    Where every custom build starts.

    $4,500 1 week · credited in full

    One week: a systems map, a written scope and a fixed statement of work per phase. Credited in full against the build.

    • One piece of real work followed end to end
    • A systems map and a written scope
    • A fixed-fee statement of work, per phase
    • Not worth it? Tell me on the last day and you don’t pay

    Start with Discovery

  • 02 Fits most businesses
    One process

    One workflow, one team, built and handed over.

    $27,500 fixed · 3 weeks

    One workflow for one team: a data model of up to 8 tables, forms and lists, one export, one integration, deployed in your cloud account and documented for the next engineer.

    • One workflow, one team, one data model of up to 8 tables
    • Forms, lists, one export, one integration
    • Deployed in your own cloud account
    • Documented well enough for the next engineer

    Start with One process

  • 03
    A system

    Several processes, several roles, the history brought across.

    from $50,000 after discovery · by phase

    Several processes and roles, 2 or 3 integrations, reporting, and years of history brought across. Scoped in discovery, built in phases with a demo every week.

    • Several processes and roles
    • 2 or 3 integrations, and reporting
    • History migrated and verified
    • Paid phase by phase, after you’ve seen each one working

    Talk about A system

  • Run plan · from $3,000 a year The infrastructure it runs on, kept up, backed up and watched. The server it runs on. Storage, and backups you can be restored from. Dependency and security updates. Monitoring, and someone who notices. Cancel at any renewal. You own the software either way.
  • That’s the starting price. A busier or more complex system costs more to run, and we agree on the number in writing along with the build, so it never comes as a surprise.
  • Not included: what you pay other companies. AI model and API keys, third-party licences and app subscriptions stay in your own accounts, at cost. I don’t mark them up.
  • The plan doesn’t include hours for changes. Each change gets its own price, agreed before I build it.
  • I’ll never take a percentage of what you sell: no royalties, no cut of transactions, no per-user fees for software you own.

Six things change the price of a Custom build, and they’re worth knowing before you ask: how consistently the work is done today, whether the system only reads documents or also has to measure drawings, whether it stands alone or connects to your accounting, how many devices and platforms are used in the field, how many outside people need a login, and whether years of history have to come across. It’s never priced per user and never licensed: you pay to have it built, and then it’s yours.

When it’s the right choice

  • The process is specific to your business and no product fits it without a pile of workarounds.
  • The workarounds have become the system: spreadsheets that are really databases, an inbox that is really a queue.
  • You need to own the system outright, because it’s how you compete.

When it isn’t

If a product on the market already does 80% of it, buy the product. I’ll tell you which one. I’d rather lose the build than sell you a worse version of something that already exists.

Not sure it’s this one?

Describe the work in a sentence or two. You’ll see which of the services it reads as, where to start, and what that costs.

  1. 01 Read
  2. 02 Weigh
  3. 03 Size
  4. 04 Result

Description

Who reads this

Cristian Penarrieta I’ll read this myself, and if we work together, I’m the one who writes the code, never a junior team or a subcontractor.

  • 20 years building software, mostly for Silicon Valley companies
  • 1 engineer, from the first call to production
  • 2 business days to hear back from me

Get in touch

Talk about software development

I’ll read your message myself and reply within 2 business days.