AI Setup

You use ChatGPT or Claude in a chat window and suspect you're getting a tenth of what's possible. You want it working on your documents, your data, your codebase — not a demo.

• A plan recommendation in Canadian dollars — which subscription or API mix fits how you work, and what it will cost per month
• Your working context set up: project instructions, reference files, memory that persists between sessions
• Claude Code installed and configured (if you build or automate): permissions, skills, and the habits that keep it safe
• Three of your real tasks done together, start to finish, so the pattern is yours
• A written runbook for you or your team — what to use when, and how to check the output

1. Snapshot. A short questionnaire and a one-page read on where AI fits your work. Free.
2. Session one. Accounts, plan, context. We set up the workspace around one real task.
3. Session two. Two more real tasks, the verification habits, and the runbook.
4. Follow-up. Two weeks of questions by email, answered by a person.

Do I need to be technical?

No. Claude Code is for people who build or automate; plenty of setups are Claude alone, used well. The snapshot tells you which you need.

Which is better, Claude or ChatGPT?

For long documents, careful writing and code, we work in Claude every day and set it up by default. If your team is already on another tool, the setup principles — context, verification, runbooks — carry over, and we say so.

Is our data safe?

We choose plan types and settings that keep your material out of model training, and we write down where your data goes. Client material never leaves the engagement.

• How to set up Claude Code properly: the setup we use every day
• Claude Code pricing in Canada, in Canadian dollars

Tell us what you’re working on. You’ll get a one-page read back from a person — what we’d do, what it would cost, and whether you need us at all.