Custom software · Lower Mainland, BC

Apps, AI and integrations, built around how you work.

Internal tools, client portals, AI assistants and the connections between the systems you already pay for. Built by the same people who run your IT, so it stays secure, supported and running after launch.

What we build

For the work no off-the-shelf product quite fits.

Four kinds of project, often combined. Most start small: one workflow that eats hours every week, fixed first.

01 / 04 · APPS
01 Apps

Web & mobile apps

Internal tools that replace the spreadsheet everyone is afraid to touch, client portals, booking and intake forms, job tracking for crews in the field. Built for the way your team already works, on hosting we manage.

  • Internal tools
  • Client portals
  • Booking & intake
  • Field & job tracking
  • Mobile-friendly web apps
  • Microsoft 365 sign-in
  • Role-based access
  • Hosting & backups
02 AI

AI assistants & automation

Assistants that answer from your own documents and policies, email and document triage, first drafts of quotes and reports, and data pulled out of PDFs and forms. Set up so your data stays yours and isn't used to train anyone's model.

  • Assistants on your docs
  • Email & ticket triage
  • Document extraction
  • Drafting & summaries
  • Meeting notes
  • Copilot & ChatGPT rollout
  • Usage policies
  • Private data handling
03 Integrations

Integrations & workflow automation

Your CRM, accounting, scheduling and Microsoft 365 or Google Workspace, talking to each other instead of through someone's copy and paste. Enter it once, and it shows up everywhere it's needed.

  • CRM & accounting sync
  • Microsoft 365 & Google
  • Power Automate
  • Zapier & Make
  • Custom APIs
  • Webhooks
  • Data migrations
  • Scheduled jobs
04 Data

Dashboards & reporting

The numbers you check every week, pulled from the systems they live in and put on one screen. No more Monday morning spent building the same report by hand.

  • KPI dashboards
  • Power BI
  • Automated reports
  • Scheduled email digests
  • Data cleanup
  • Single source of truth
  • Alerts & thresholds
  • Exports for accounting
How a project runs

First conversation to launch.

Small automations are often live within a couple of weeks. Larger apps ship in stages, so you're using something real early instead of waiting on a big reveal.

Typical first version · approximateWhat you get
Step
Wk 1Wk 2Wk 3Wk 4Wk 5Wk 6
01Discovery
02Proposal
03Build
04Launch
01 · Discovery

We learn how the work happens

We sit with the people doing the job, look at the tools and spreadsheets in use today, and find where the hours actually go. Sometimes the answer is a setting in software you already own, and we'll say so.

A short write-up of the problem and what fixing it is worth.
02 · Proposal

A fixed scope for the first version

What it will do, what it won't, what it runs on and what it costs. The price doesn't move unless the scope does.

A written proposal and a fixed price for version one.
03 · Build

Short cycles, regular demos

You see working software as it comes together, not a slide deck. Feedback goes in while it's still cheap to change.

A working version your team has already tried.
04 · Launch

Live, documented, yours

We deploy it, train the people using it and hand over the documentation. You own the code and the data. Hosting, updates and changes afterwards are available, never required.

The live app, documentation, and the source code.

A single automation or integration usually fits in the first couple of weeks. Every project gets its own schedule in the proposal.

Built on what we run

Software from the people who already support your IT.

Where we work

Local when it helps, remote when it doesn't.

Most of the building happens remotely, but discovery and training go better in person. We meet clients on site across Metro Vancouver and the Fraser Valley, and work remotely with businesses anywhere in BC.

Common questions

Before you start a project

01Should we build something or buy a product?
Buy, when a product does the job. It's cheaper and someone else maintains it. Build when you've tried the products and they force your team into workarounds, or when the real problem is that your existing tools don't talk to each other. Discovery is where we work out which it is, and we'll tell you if the answer is a subscription you can buy today.
02What does a custom project cost?
It depends on the size. Connecting two systems or automating one workflow is a small, fixed-price job. A full app with its own logins and database is a larger one, and we usually split it into stages so you're paying for something working at each step. Either way you get a fixed price for the first version before any work starts.
03Who owns the code and the data?
You do. The source code, the data and the accounts it runs on are yours, and you get the documentation at handover. If you ever want another developer to take it over, nothing is locked to us.
04Is our data safe with AI tools?
It can be, if it's set up properly. We use business accounts and APIs whose terms don't allow your data to be used for training, keep access limited to the people who need it, and choose what the AI can and can't see. We also help write a short AI use policy, so staff know what's okay to paste into a chatbot.
05Can you work with the software we already use?
Usually, yes. Most business software, including Microsoft 365, Google Workspace, accounting, CRM and scheduling tools, has a way to connect to it. Where there's no clean connection we'll find the most reliable workaround and tell you its limits up front.
06How long does a project take?
A single automation or integration is often live in one to three weeks. A new app usually has a first usable version in four to eight weeks, then improves in stages from there. The proposal gives you a date for the first version.
07Who maintains it after launch?
We can host it, keep it updated and make changes as your business changes, the same way we look after the rest of your IT. That's optional. Because you own the code and documentation, you can also take it in-house or to someone else.
08Do you do small projects?
Yes. A single report that builds itself, a form that files its answers in the right place, or an assistant that answers staff questions from your handbook are all normal jobs for us, and they're often the best place to start.
Start a project

Tell us what's slowing you down

A couple of sentences about the problem is enough to start. Which tools you use today and who does the work now helps. We'll come back with a time to talk or a first rough idea, whichever you need first.

PDF, image or Office file. Up to 10 MB.

We reply within one business day. Your details are only used to get back to you about this project.