Services

Six systems. One operator.

We map where your time goes, then build and run the systems that take it back. Every one wired into the tools you already use — and built to keep running without you watching it.

Who we work with

Owner-led businesses, 3–50 people

Where

Sea-to-Sky based, working everywhere

What it usually looks like

Operations running on spreadsheets, email and one very busy person

01Ops Mapping & Audit 02AI Agents 03Automation Pipelines 04Internal Tools & Dashboards 05Content Systems 06Web Systems
01

Start here

Ops Mapping & Automation Audit

Before anything gets built, we find out where the hours actually go — and which ones are worth buying back.

Signs you need this

  • You know the business wastes time, but you couldn't say where if someone asked.
  • Every quote you've had for automation starts with software you'd have to learn.
  • The same three jobs get done manually every week and nobody remembers why.

What you get

  • One working session — a walkthrough of a normal week, one job traced end to end, and your dread list.
  • A scored Process Inventory — every recurring task rated on hours per month, pain, and how automatable it really is.
  • A one-page Automation Map — what to automate, in what order, and what to deliberately leave alone.
  • A plain-language estimate for the first build, with no obligation to do it with us.
Book a Map session Most engagements start here. Some stop here — that's a fine outcome too.
02

Service

AI Agents

Assistants that do the job, not chat about it. Research, triage, drafting, reporting — connected to your real tools, with real guardrails.

Signs you need this

  • Somebody skilled spends hours on work that is mostly reading, summarising and re-typing.
  • You've tried a chatbot, got confident nonsense, and quietly stopped using it.
  • The judgement calls are repeatable — it's the volume that's the problem.

What you get

  • Agents wired to your systems — not a chat window. They read from and write to the tools the work already lives in.
  • Guardrails by design — defined scope, a human approval step wherever it matters, and nothing published without a sign-off.
  • Document and inbox handling — extraction, triage, routing and drafted replies for the volume that never ends.
  • Failure alerts — when an agent can't do the job, you hear about it immediately instead of discovering it later.
Talk through an agent → Not sure it's an agent problem? Start with the Map session.
03

Service

Automation Pipelines

The 6am work, done by 6:02. Files fetched, schedules ingested, reports built, the team notified — before anyone's up.

Signs you need this

  • Someone's first hour is spent downloading, copying and re-formatting the same files.
  • Two systems hold the same information and a person is the integration between them.
  • When that person is away, the morning simply doesn't happen.

What you get

  • Scheduled jobs that fetch, transform and deliver on their own — daily, hourly, or on a trigger.
  • API and webhook integrations between the tools you already pay for, so nothing gets re-typed.
  • Catch-up logic — if a machine was asleep or an upstream system was down, the job runs when it comes back.
  • Alerting that names the failure, routed to you or the team, so a silent break can't run for a week.
Describe your 6am → If it happens every day at the same time, it's a candidate.
04

Service

Internal Tools & Dashboards

The spreadsheet everyone fights over, replaced by something built for the job — live, shared, and honest about who changed what.

Signs you need this

  • The business runs on one spreadsheet and everybody has a slightly different copy of it.
  • Answering "where are we at?" means asking three people and reading a chat thread.
  • You've priced real software and it's either too much money or too much process.

What you get

  • A live board for the thing you actually manage — jobs, shifts, approvals, pipeline — on one URL that's always current.
  • Role-appropriate access — the crew sees today, you see everything, clients see only their own.
  • An audit trail — who changed what, when, kept append-only so month-end reconciles.
  • Wired to the same systems as everything else, so the board and the automations never disagree.
Show us the spreadsheet → Send the file. It usually tells us the whole story.
05

Service

Content Systems

SEO engines and social pipelines that draft on-brand, route to you for approval, and publish on schedule. Approval takes two minutes a week.

Signs you need this

  • Marketing happens in bursts, then stops for a month because you got busy.
  • Approving content means a long email thread and three rounds of "can we change one line".
  • You're paying for content that doesn't sound like you, and fixing it yourself.

What you get

  • Drafting in your voice — built from a brand-voice session and a per-client rule list, not a generic prompt.
  • A weekly review link — everything queued on one branded page. Approve, request a change, or deny, per item.
  • Nothing publishes without you. Anything you don't approve simply stays in the queue.
  • Scheduled multi-platform publishing — website, Instagram, Facebook, LinkedIn, Google Business Profile — from one approval.
  • A feedback loop — your change requests become rules the system won't break twice.
See a live review link → We'll send you a real one to tap through.
06

Service

Web Systems

Sites built to be operated by machines as well as people — instrumented from analytics through to the ad account.

Signs you need this

  • Your site is a brochure — nothing feeds it and nothing comes out of it.
  • You can't change a page without emailing whoever built it.
  • You're spending on ads that land on pages nobody optimised for the search that sent them.

What you get

  • Fast, accessible builds — WordPress, Next.js or headless, chosen for who has to maintain it, not for our convenience.
  • Local SEO architecture — service and location pages structured to rank, with the schema and internal linking done properly.
  • The ad account that matches — campaigns, negatives and landing pages built as one job instead of three.
  • Tracking that's actually correct, so you can tell which spend produced which enquiry.
  • You own it outright — accounts, code, content, on your infrastructure.
See the First Chair offer → A rebuild plus an SEO audit, one flat monthly number.

Engagement

How a build actually goes

Same three phases whichever service you start with. The point of the shape is that your time in it stays small.

01

Map

One working session on your normal week. We score every recurring job and hand back a one-page automation map with an order of attack.

Your time: 2 hours, once
02

Build

Weekly releases against that map, smallest painful thing first. You see working software every week, not a status report.

Your time: ~15 min/week
03

Run

You run the system; we watch it, tune it and keep it fast. Flat monthly. When something drifts, we know before you do.

Your time: ~10 min/week
How we work together Build phase billed hourly. Running it is a flat monthly retainer — and you can stop it.

Contact

Tell us what's eating your time.

hello@blkdmd.ca

One email. We'll reply with three questions and, if it's a fit, a working session on the calendar within the week. Whistler, BC — working everywhere.