Concept illustration: Canon guides two assistants as they join and inspect graphite modules at a workshop bench.

AI-native Technical support

Put AI to work.
Bring your
team with it.

Products, education and hands-on support.
Put ChatGPT and Codex to use in your team’s work.

Talk through your workflow ↗

Support from $900/month See plans ↓

Original conceptual illustration / people approve the work01 / Learn · Build · Run
An illustrative workflow trace, not live activity. The full service story is readable below.
Learn · Build · RunProducts & workLook inside

01 / Learn → Build → Run

Start with one task.
Make the next step clear.

Concept illustration: Canon steadies connected graphite modules while another agent inspects the joint with a loupe.
Connection, then verification. A conceptual view of the work—not delivered hardware.
01 / LEARN

Work through an example.

Short lessons and guided practice in the tools your team will use.

02 / BUILD

Connect it to the work.

Agree the scope, then build and test a useful workflow together.

03 / RUN

Review it. Keep the context.

Micah is accountable for the service. Your team keeps approval authority.

See the products and work

02 / From the task to the work

Make it useful.
Make it yours.

Start with something your team already does. Give AI a clear task, keep a person at the decision, and build from there.

One possible workflow

Illustrative example
Not a client delivery

  1. 01 / INPUT

    Bring the notes.

    A team member collects the approved notes from a project meeting.

  2. 02 / DRAFT

    Give AI a first pass.

    ChatGPT turns those notes into a draft with decisions, owners and open questions.

  3. 03 / REVIEW

    The team makes the call.

    A person checks the source, corrects the draft and approves what gets shared.

A product we built / Draw

Before you automate it,
draw it.

Put the steps, tools and people on one canvas. Mark the places where someone needs to approve the work.

Explore the working canvas

Selected client work

Built. Published.
Open to inspection.

Websites and content systems from our wider practice. These projects show delivered work; they are not evidence of client adoption of OpenAI tools.

MaverickX website, showing its chemistry-focused homepage

MaverickX

Web development

A website presenting chemistry across energy, mining and water treatment.

Inspect the work

CREATE SOMETHING web development. The image is an existing project reference; the live website may change.

Open the full reference image ↗Visit MaverickX ↗

A useful workflow needs a clear scope.
Here’s what support includes.

See what’s included

LOOK INSIDE / THE WORKING BOUNDARY

What can the agent
see and do?

Give it the context to do the work. Set the limits before it starts. Keep the result open to review.

ACCESS IS A BOUNDARY.

A useful instruction
is only the beginning.

Illustrative system detail. Explore the controls beside it.
01ContextThe right information, within reach.

Choose the documents, records and tools the agent can use for this workflow. Keep sources and their limits visible.

Missing access or an out-of-date source is a reason to ask, pause or mark the answer uncertain.

02PermissionA clear limit on what can happen.

Instructions describe the rules. The host and connected tools enforce access: which records can be read, which actions can run, and which need approval.

A boundary before executionSchematic: a requested action passes through a permission boundary before a tool can act. A blocked request stops at the boundary.REQUESTHOST / TOOL GATEACTION
Requested actionPermission checkRun · ask · stop

Approval applies to the stated action and scope. A refusal stops that action; it does not grant a workaround.

03OutputWork you can check and use.

Review the actual result against the agreed task: the changed file, the updated record or the delivered answer. Keep the checks and unresolved issues beside it.

A receipt records what happened. Correctness still needs evidence from the output and its checks.

04UsageKnow what was used. Know what is missing.

Use provider records where available to report usage and cost. Label estimates separately, with their assumptions. Missing records remain unknown.

Agree the budget and approval point before work starts. If usage cannot be confirmed, pause for review instead of assuming there is room to continue.

A model of how we scope work. Controls and available records depend on the tools connected to your workflow.

04 / Bring your team with youPeople keep the decisions.

Built together.
Used by your team.

A working system needs people who know how to use it. We make room for practice, questions and a clear handoff.

Concept illustration: Canon shares a working guide while two assistants practice with the connected modules.
Shared practice and handoff / conceptual illustration.
01 / OWNER

Someone knows the work.

Micah Johnson currently delivers the service, with agents assisting the work. Your team keeps approval authority.

Meet Micah
02 / PRACTICE

Try it together.

Use attended remote sessions to work through real tasks. Ask questions while the tools and decisions are in front of you.

03 / HANDOFF

Keep the context.

Each milestone includes verification and a handoff. Keep the agreed code, tests, instructions and project history.

05 / Ongoing supportCancel before renewal.

A steady place
to move the work.

Choose the capacity that fits your team.
We agree on scope before work begins.

Focused

One agreed workstream

$900/month

For one workflow that needs attention.

Workstreams
1
Milestones per month
1
Check-ins per month
2 × 30 min
Remote sessions per month
2 × 60 min
Revision rounds per milestone
1
Discuss Focused

Team

Up to two workstreams

$2,500/month

For more work moving together.

Workstreams
2
Milestones per month
2
Check-ins per month
2 × 30 min
Remote sessions per month
4 × 60 min
Revision rounds per milestone
1
Discuss Team

One milestone means one agreed workflow map or one scoped improvement. It includes an acceptance check, verification, a handoff and one feedback and revision round.

Both plans include skills, learning resources and Slack support. Resource access, session times and response times are confirmed before payment.

Need ongoing live operations?

Control is a separate service, from $900/month
Before we begin Scope, costs & ownership
What needs a separate agreement?

Larger Builds, managed Control and production incident response need separate agreements. Membership capacity covers the agreed workstreams and milestones above.

What costs extra?

Project-specific AI development, testing and production usage, hosting and third-party services are budgeted separately. You approve the budget first.

Our everyday coding tools are our expense. More API credit does not add delivery capacity.

Who delivers the service?

Micah Johnson currently delivers the service, with agents assisting the work. The dedicated member portal is in development.

We confirm resource access, session times and response times before payment.

What does our team keep?

After full payment, you own commissioned deliverables under your agreement, except reusable provider tools, which are licensed for continued use.

You keep the agreed code, tests, instructions and project history.

Can we cancel?

Cancel before your next renewal by emailing [email protected] to stop future membership charges. Support continues through your paid period while we hand over your code and documentation, document open work, and plan the transition. If you need more help afterward, we’ll agree on the scope and price before extending support.

Separately scoped projects follow their agreed terms.

Read the full service details
06 / Start with one taskMake the next step clear.

What would you
like working better?

Talk through your workflow

Bring the tools involved and an example of the result you need. We’ll discuss fit, then agree on the work and how to check it.

Explore the work library Films, source and field reports +