Know where you stand.
Move Forward with Canon.

It’s time to level up the way you work with AI. Give AI the context to do more with each prompt—less typing and manual documentation, faster everyday work, and more accurate answers about your work or business.

Start here Connect with a Business Engineer

Keep your contextBuild on what you already know.

See what is trueTrace answers to the right sources.

Understand your optionsMake assumptions and gaps visible.

Keep work in syncLet agents carry changes forward.

One account. Your scope.

Start with the authoritative reality
that already exists.

Begin where you want ForwardCanon to help: with your own work, with an existing business, or with a team. We establish what is already authoritative in that scope and build from there. Every participating person still establishes or reuses a Personal Canon, but business and team discovery do not have to wait for personal setup to come first.

Individual

For you

Start from the work, sources, and context you already have. Build durable personal context that your agents can use across conversations.

Less typing. More context in every answer.

Explore individual use

Business

For your business

Start from the business evidence and owner knowledge you already have, then map it through Demand, Supply, Supply Optimization, and Profit Management.

Understand your options before you commit.

Explore business control

Team

For your team

Start from existing people, responsibilities, systems, and shared work, then connect each participant through clear identity, access, and authority.

Coordinated work, with leadership in control.

Explore shared team operation

You do not need to choose an account type here. Your agent helps establish individual, team, or business scope during setup. Team Setup can operate without Business Control.

Start with a conversation

Your agent helps
you get established.

Begin with yourself, your team, or your business. Your first conversation finds the right scope from what you want to accomplish and what is already authoritative.

The planned free trial includes guided setup and useful first work. Trial duration and usage limits will be published before activation.

Create your account.
Set up your email and password, then verify your mobile phone number by text message. Two-step verification is required. Your account page is also where you manage connections and billing.
Talk it through with your agent.
Explain your goals and bring existing sources. Your agent helps establish identity, responsibilities, roles, and authority. Ask questions about the system as you go.
Review your first Canon.
Check the understanding together, correct it, and initialize your first canonical state. Unanswered questions stay visible.
Put it to work.
Use the trial to experience maintained context. Documentation and resources are available from every repository, and your agent helps you understand and use them.

From a question to a next step

What prompting with Canon looks like

Ask for what you need, in your own words. AI finds the right context, organizes the work, and suggests a consistent home for recurring tasks—so a fresh chat can pick up from what is saved.

Everyday requests. Separate chats.

A workweek with a consistent home

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“What does my workday look like today?”

Illustrative answer

Your client proposal is due tomorrow, so that comes first. You have room for the redesign afterward, but its deadline is still open. I’ve pulled today’s priorities from your calendar and current project records.

Sources and saved context: Calendar · Current tasks · Project deadlines
Still unknown: The redesign deadline still needs confirmation.

What I can take on next

Since you plan your week regularly, I suggest a Work week space in your canon for your schedule, priorities, and unfinished tasks. I can organize it and keep it current as we work.

YOU ASK IN A NEW CHAT

When you decide to keep a regular weekly plan

“Help me keep my workweek organized.”

Illustrative answer

I’ve created Work week in your canon and linked it to your calendar and active projects. Each week has a dated plan, with priorities, deadlines, and unfinished work carried forward. I’ll use this as the home for your day and week questions.

Saved context retrieved: Your request for ongoing planning · Calendar · Active projects · Saved Work week space
Still unknown: The redesign deadline is still unconfirmed.

What I can take on next

I can organize the rest of this week around the proposal and existing appointments, then keep the plan aligned as work changes.

YOU ASK IN A NEW CHAT

The next Monday, in a fresh chat

“What does my week look like?”

Illustrative answer

The proposal is now recorded as sent. The redesign is due Friday, with a review slot still to confirm. I’ve built this week’s plan in Work week from your current calendar and project updates, carrying forward only unfinished work.

Saved context retrieved: Work week · Current calendar · Recorded proposal submission · Updated redesign deadline
Still unknown: The reviewer has not confirmed a time.

What I can take on next

I can draft the review request and arrange the remaining work around that dependency.

Everyday requests. Separate chats.

A launch that keeps its history

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“Where did we leave off with the launch?”

Illustrative answer

I found your launch project. You chose the smaller first release and deferred reporting; client access is still an open decision. The plan and decision history are already together in the project.

Sources and saved context: Decision history · Launch scope · Open questions
Still unknown: The client access requirement has not been settled.

What I can take on next

I can pick up the plan and show what each client-access option would change.

YOU ASK IN A NEW CHAT

A later planning session

“Keep the launch small. Client access can wait.”

Illustrative answer

The launch scope now keeps client access for a later release alongside reporting. The first release stays focused on the smaller scope you already chose.

Saved context retrieved: Client launch · The original scope decision, deferred reporting, and your new client-access decision.
Still unknown: The later release date has not been agreed.

What I can take on next

I can update the launch plan and keep the deferred features visible.

YOU ASK IN A NEW CHAT

Before a client meeting

“Why did we leave reporting out of the launch?”

Illustrative answer

Reporting was deferred to preserve the smaller first release. Adding it would reopen that scope decision and require a fresh estimate; client access is still deferred separately.

Saved context retrieved: Client launch · The original decision and the later confirmation that client access could wait.
Still unknown: The added effort has not been estimated.

What I can take on next

I can prepare a scope comparison and the decision history without changing the approved plan.

Everyday requests. Separate chats.

One deadline, connected work

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“The client delivery moved to Friday. What needs to change?”

Illustrative answer

The review and handoff both depend on that date. I’ve noted the change in the existing delivery project and found the affected tasks. Is Friday your internal target or the date agreed with the client?

Sources and saved context: Project schedule · Task dependencies · Update permissions
Still unknown: It is unclear whether Friday is your internal target or the agreed client deadline.

What I can take on next

I can clarify the deadline, sync the authorized changes, and flag any remaining scheduling conflicts.

YOU ASK IN A NEW CHAT

Later that afternoon

“Friday is agreed with the client. Update the delivery plan.”

Illustrative answer

Friday is now recorded as the external commitment. The review and handoff plan uses that date, and any dependent task that no longer fits is flagged.

Saved context retrieved: Client delivery · The earlier deadline change, review dependencies, and your confirmation of the client agreement.
Still unknown: A reviewer still needs to confirm availability.

What I can take on next

I can sync the authorized schedule updates and show the unresolved review dependency.

YOU ASK IN A NEW CHAT

The following morning

“Can we still make Friday’s client delivery?”

Illustrative answer

The saved delivery plan still targets Friday, but it depends on an unconfirmed review slot. I’ve checked the remaining tasks against that commitment and brought the review gap forward.

Saved context retrieved: Client delivery · The confirmed deadline and unresolved dependency from the maintained project plan.
Still unknown: The reviewer has not committed to a slot.

What I can take on next

I can draft the review request and show a revised handoff plan once availability is confirmed.

Everyday requests. Separate chats.

Client paperwork, through to submission

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“Submit Morgan’s client summary. Let me know if it fails.”

Illustrative answer

Morgan’s summary is submitted through the approved portal. I used the saved template and current client details, then filed the completed document and receipt with Morgan’s record.

Sources and saved context: Saved template · Current client record · Authorized submission route · Portal receipt
Still unknown: Submission is confirmed. The recipient’s review is still pending.

What I can take on next

I can check the remaining paperwork and prepare what is due next. If a submission fails, I’ll tell you and keep it marked incomplete.

YOU ASK IN A NEW CHAT

After a client update

“Morgan moved to 18 Cedar Lane. Submit a corrected summary.”

Illustrative answer

The client record is updated, and a corrected summary has been submitted with its own receipt. The earlier submission stays in the history, clearly marked as superseded.

Saved context retrieved: Morgan’s client record · Morgan’s original submission, saved template, authorized address change, and new receipt.
Still unknown: The corrected submission is confirmed; recipient processing is still pending.

What I can take on next

I can check Morgan’s other active forms for the old address and bring you the ones that also need correction.

YOU ASK IN A NEW CHAT

At the next appointment

“Submit Morgan’s follow-up form.”

Illustrative answer

The follow-up form is filled and submitted using its saved template and Morgan’s current record, including 18 Cedar Lane. Its receipt is saved alongside the earlier documents.

Saved context retrieved: Morgan’s client record · The updated client record, follow-up template, approved submission route, and confirmed receipts.
Still unknown: All required fields were available. Submission and recipient review remain separate statuses.

What I can take on next

I can put together Morgan’s paperwork status—what is submitted, what is awaiting review, and what is due next—so you only need to address the exceptions.

Everyday requests. Separate chats.

A new project, with room to deliver

Chat 1 of 3

YOU ASK IN A NEW CHAT

With the new website brief attached

“Can I fit this website project into my schedule?”

Illustrative answer

A smaller scope fits after your current handoff; starting this week overlaps two deadlines. I’ve filed the brief and capacity comparison under a proposed Website refresh project, with the start date and effort still open.

Sources and saved context: Current commitments · Available work time · Proposed project scope
Still unknown: The new project’s effort and start date still need agreement.

What I can take on next

I can compare a later start and a smaller scope, then record the option you choose.

YOU ASK IN A NEW CHAT

After speaking with the client

“The website client accepted the smaller scope and later start. Let’s do it.”

Illustrative answer

The new project is recorded with the smaller scope and later start. Your current commitments stay in place, and the handoff remains a dependency.

Saved context retrieved: Website refresh · The capacity comparison and the client agreement you just supplied.
Still unknown: The detailed effort estimate still needs validation.

What I can take on next

I can add the agreed project and show its timing alongside existing commitments.

YOU ASK IN A NEW CHAT

When plans change

“My current handoff slipped two days. What does that affect?”

Illustrative answer

The new project depends on that handoff, so its planned start needs review. The smaller scope is still the agreed scope; a delay does not silently change that agreement.

Saved context retrieved: Website refresh · The recorded dependency, later start, and approved smaller scope.
Still unknown: The new client has not agreed to a revised start date.

What I can take on next

I can show the affected schedule and prepare the start-date discussion.

Everyday requests. Separate chats.

From revenue to a growth decision

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“Where is our customer money coming from?”

Illustrative answer

Repeat service brings in the most collected revenue. I’ve grouped payments by stream and customer, separated unpaid invoices, and kept the breakdown in your revenue review so we can build on it.

Sources and saved context: Customer payments · Posted invoices · Revenue-stream mappings
Still unknown: A few payment descriptions do not identify a unique service; those remain outside the confirmed totals.

What I can take on next

I’d like to connect that revenue to the labor, equipment, and direct costs behind it, then bring you a view of which work is contributing the most.

YOU ASK IN A NEW CHAT

At the next planning session

“Which services are worth growing?”

Illustrative answer

I compared the mapped revenue with the linked delivery costs. Repeat service leads on direct contribution in the fully matched records; I’ve kept incomplete cost coverage separate from that result.

Saved context retrieved: Revenue review · Saved breakdown · Linked labor and delivery costs
Still unknown: Shared overhead still needs a confirmed allocation before calling this a full profit comparison.

What I can take on next

I’d like to match the strongest work to your available capacity and bring you a growth plan that shows where the current team has room.

YOU ASK IN A NEW CHAT

Before deciding where to grow

“Can our team handle more repeat-service work?”

Illustrative answer

I matched the repeat-service work to the roster, job durations, and current bookings. There is capacity in the quieter windows; the peak window remains constrained. I’ve separated usable capacity from hours already committed.

Saved context retrieved: Revenue review · Contribution comparison · Roster · Current bookings
Still unknown: Extra sales are not guaranteed, so the growth scenarios still carry demand assumptions.

What I can take on next

I’d like to prepare a targeted booking and scheduling proposal for those quieter windows, with the expected contribution and the limits made clear.

Everyday requests. Separate chats.

An improvement AI helps carry through

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“We’re busy. Why aren’t we making more profit?”

Illustrative answer

Lower-margin work and rework-driven overtime are absorbing the extra revenue. I’ve added the diagnosis and supporting records to an open Rework and margin issue in your business canon.

Sources and saved context: Revenue by stream · Labor costs · Rework records · Cost allocations
Still unknown: Shared overhead allocation still needs validation before the final margin is confirmed.

What I can take on next

I’d like to isolate the repeat causes of rework and bring you a small trial that targets the biggest avoidable cost, with a baseline for judging the result.

YOU ASK IN A NEW CHAT

After reviewing the proposal

“Let’s try the rework fix you proposed.”

Illustrative answer

I’ve set up the approved two-week checklist trial for the affected job type, linked the instructions to the team’s work, and saved the current rework and labor figures as the baseline.

Saved context retrieved: Rework and margin · The margin diagnosis, proposed fix, approved trial scope, and recorded baseline.
Still unknown: The trial has started; its operating result is not yet known.

What I can take on next

I can assemble the trial results from the job records and bring you the change in rework, labor cost, and delivery time against that baseline.

YOU ASK IN A NEW CHAT

After the trial results are recorded

“Did the rework trial help?”

Illustrative answer

Rework time and overtime cost both fell in the trial records, while delivery volume stayed comparable. I’ve separated the measured saving on the trial jobs from any broader claim about company profit.

Saved context retrieved: Rework and margin · The saved baseline, completed trial jobs, time records, and actual labor costs.
Still unknown: We have not yet established whether the improvement holds across the full service line.

What I can take on next

I’d like to prepare a staged rollout with the same measures, so you can see whether the saving holds before extending the change further.

Everyday requests. Separate chats.

From a staffing question to measured coverage

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“Do we need another hire, or a better schedule?”

Illustrative answer

The current team has capacity, but coverage misses peak demand. I’ve compared a schedule change with another hire and saved the open issue as Peak-hour coverage alongside your staffing records. We have a place to continue when you’re ready.

Sources and saved context: Work schedule · Payroll costs · Booked work
Still unknown: The schedule option fits confirmed availability; sustained future demand is still an assumption.

What I can take on next

I’d like to turn the schedule option into a short trial and bring you a coverage plan, the expected cost difference, and the conditions that would justify a hire instead.

YOU ASK IN A NEW CHAT

After reviewing both options

“Let’s try the schedule change we discussed earlier this week.”

Illustrative answer

I found the Peak-hour coverage issue from earlier this week. I’ve applied the approved trial within confirmed availability and recorded it with the original roster and hiring comparison, ready to measure the result.

Saved context retrieved: Peak-hour coverage · The two staffing options, confirmed availability, approved trial, and original roster.
Still unknown: The trial still needs actual coverage and service results.

What I can take on next

I can compare wait times, uncovered hours, and labor cost as the trial records come in, then bring you the evidence for keeping or changing the schedule.

YOU ASK IN A NEW CHAT

After the schedule trial

“Did the new schedule solve our coverage problem?”

Illustrative answer

The trial covered the original peak-hour gap without an added hire in the recorded period. I’ve updated the same staffing issue with actual coverage and labor costs; future demand still needs watching.

Saved context retrieved: Peak-hour coverage · The trial roster, service results, actual labor costs, and saved hiring scenario.
Still unknown: A seasonal increase could exceed this capacity; the trial does not settle future demand.

What I can take on next

I’d like to present a clear hiring trigger based on sustained workload, coverage, and cost, so the next decision starts from evidence you already have.

Everyday requests. Separate chats.

AI carries the analysis into a testable proposal

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“How do we make field service profitable?”

Illustrative answer

Current pricing does not cover the labor and equipment time. A pricing test is the simpler first option. I’ve kept the costs, alternatives, and open questions together under the existing Field service stream.

Sources and saved context: Stream revenue · Resource allocation · Job duration · Operating costs
Still unknown: Customer response to a price change and the cost of changing the process are not yet established.

What I can take on next

I’d like to turn that option into a scoped test proposal, showing the price range, expected contribution, customer-response assumptions, and the decision needed to start.

YOU ASK IN A NEW CHAT

When reviewing the proposal

“What would a field service pricing test look like?”

Illustrative answer

I’ve drafted a limited pilot for the existing delivery process, with a defined job scope, proposed prices, and measures for acceptance, completed work, and actual contribution.

Saved context retrieved: Field service record · Cost gap · Compared options · Delivery baseline
Still unknown: The test price and scope still need the owner’s decision.

What I can take on next

I can prepare the operating instructions and baseline report around the option you choose, so the team can begin with a complete test package.

YOU ASK IN A NEW CHAT

After the approved pilot produces results

“Is field service starting to pay for itself?”

Illustrative answer

The completed pilot jobs cover their linked delivery costs at the tested price. I’ve updated the model with actual acceptance and job results, while keeping shared overhead visible in the full stream assessment.

Saved context retrieved: Field service record · Approved pilot · Actual acceptance and job results
Still unknown: The pilot does not yet establish that the whole stream covers its share of overhead at sustained volume.

What I can take on next

I’d like to present the remaining break-even gap and compare a wider pricing rollout with the delivery-process option we kept on record.

Everyday requests. Separate chats.

A reinvestment proposal with its reasoning intact

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“What can we afford to put back into the business?”

Illustrative answer

After allowing for your agreed reserve and upcoming commitments, part of the demonstrated surplus could address the equipment bottleneck. I’ve added the comparison to your reinvestment plan; quotes and expected gains still need checking.

Sources and saved context: Validated operating results · Cash commitments · Reserve policy · Capacity constraints
Still unknown: The equipment quote and expected improvement still need verification.

What I can take on next

I’d like to bring you a reinvestment proposal comparing cash retention, buying, and leasing, with cash timing, obligations, and the evidence for the capacity improvement.

YOU ASK IN A NEW CHAT

When reviewing the options

“Should we buy or lease the equipment we looked at?”

Illustrative answer

Using the verified quotes, buying has the lower total cost while leasing preserves more near-term cash. Both fit the recorded reserve boundary. I’ve set out the cash trade-off and the assumptions behind the capacity gain.

Saved context retrieved: Reinvestment plan · The demonstrated surplus, agreed reserve, verified quotes, and measured bottleneck.
Still unknown: How much flexibility you want to retain is an owner preference the cost comparison cannot decide.

What I can take on next

I’d like to present a recommendation under each cash-priority choice, including the result we would measure after installation. The spending decision stays with you.

YOU ASK IN A NEW CHAT

When comparing a different direction

“Why invest in that equipment before another location?”

Illustrative answer

The equipment case addresses an observed bottleneck with a verified cost. A second location introduces a separate demand and operating model. I’ve retained the equipment comparison so we can evaluate expansion alongside it.

Saved context retrieved: Reinvestment plan · The original bottleneck evidence, equipment options, reserve policy, and current operating results.
Still unknown: Demand and operating costs for a second location are not yet established.

What I can take on next

I’d like to build a first expansion case from the reusable parts of your current model and return with the location-specific evidence we still need.

Everyday requests. Separate chats.

Team progress without chasing updates

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“What did Timmy get done last week?”

Illustrative answer

Timmy completed the dispatch setup guide, closed three tasks, and updated the shared checklist. I’ve pulled those results from his Operations work records. One job is awaiting review and remains outside the completed total.

Sources and saved context: Completed work records · Shared document revisions · Task ownership · Your team-view permissions
Still unknown: One submitted job is still awaiting review, so it is not counted as finished.

What I can take on next

I’d like to turn this into a team progress brief that shows completed work, blockers, and where a decision from you would help.

YOU ASK IN A NEW CHAT

While reviewing the week

“What’s blocking Timmy, and can we help?”

Illustrative answer

The remaining job is waiting on a project-lead review, not another task from Timmy. I’ve pulled together the submitted work, review criteria, and the specific approval still needed.

Saved context retrieved: Timmy’s Operations work records · Timmy’s weekly work record, the pending job, and the assigned review responsibility.
Still unknown: The project lead has not recorded a decision.

What I can take on next

I can prepare a concise review brief for the lead and identify work Timmy can move forward while that decision is pending.

YOU ASK IN A NEW CHAT

The following week

“How did Timmy get on this week?”

Illustrative answer

The lead’s review is now recorded, and the previously blocked job is complete. Timmy has also finished the next checklist revision. I’ve separated those new results from the items already counted last week.

Saved context retrieved: Timmy’s Operations work records · The previous weekly snapshot, newly recorded approval, completed job, and document revisions.
Still unknown: The next assigned job is in progress and remains outside the completed totals.

What I can take on next

I’d like to show how those completed items moved the department’s milestones, with the remaining dependencies and owners alongside them.

Everyday requests. Separate chats.

Useful work already exists in your company

Chat 1 of 3

YOU ASK IN A NEW CHAT

From the existing onboarding project

“Does the team already have resources for this project?”

Illustrative answer

I found a rollout checklist, training deck, and similar project timeline shared with your role. I’ve linked the useful sections, owners, and versions to your onboarding project so the next draft can use them.

Sources and saved context: Project goals · Accessible team uploads · Document versions · Source owners
Still unknown: The previous timeline assumed a smaller team; those dates need adapting.

What I can take on next

I’d like to assemble a project starter pack from those resources, adapt it to your scope, and show which assumptions need updating.

YOU ASK IN A NEW CHAT

After seeing the available resources

“Put together a first draft for the onboarding project.”

Illustrative answer

The starter pack is drafted against this project’s goals using the shared checklist, training sections, and timeline structure. Each reused piece links back to its source and owner; the old project’s dates were not carried over.

Saved context retrieved: Operations onboarding · The accessible uploads, source versions, project goals, and identified timeline differences.
Still unknown: The project-specific dates still need agreement.

What I can take on next

I can turn the draft into a proposed delivery plan using the department’s current workload and bring you the scheduling choices.

YOU ASK IN A NEW CHAT

After the source material changes

“Have the source documents for our onboarding draft changed?”

Illustrative answer

Support has revised the handoff instructions in its training deck. I compared that version with the one used in your draft and marked the affected sections, with the source change attached.

Saved context retrieved: Operations onboarding · The starter pack’s source references, saved versions, and the newly shared revision.
Still unknown: Whether to adopt the revised handoff is still a project decision.

What I can take on next

I can prepare an updated draft and a short impact summary so you can decide whether the new instructions belong in this project.

Everyday requests. Separate chats.

From department goals to visible progress

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“Start an Operations project to speed up job assignments. Give the department access.”

Illustrative answer

I’ve created Job assignment turnaround under Operations, using the department’s existing roles and your admin authority. Its goals, work, and progress will stay together. What turnaround time do you want, and by when?

Sources and saved context: Confirmed department membership · Existing access roles · Your project-admin authority
Still unknown: The initial goals are yours to set; none have been inferred.

What I can take on next

Once you give me the target, I can prepare milestones, suggested owners, and a first work plan from existing company resources.

YOU ASK IN A NEW CHAT

From the new Operations project

“Assign jobs within one business day by the end of next month.”

Illustrative answer

That goal is recorded with its target date. I’ve drafted four milestones: an intake checklist, routing rules, a live pilot, and a timing review. Proposed owners come from Operations’ existing responsibilities.

Saved context retrieved: Job assignment turnaround · The department project, its access scope, your goal and deadline, and existing team responsibilities.
Still unknown: The proposed assignments and plan are awaiting your approval.

What I can take on next

I can prepare the intake checklist and routing proposal from your existing resources, giving the team concrete material to begin with once you approve the plan.

YOU ASK IN A NEW CHAT

After the approved project is underway

“How’s the Operations job-assignment project going?”

Illustrative answer

Two of four milestones are complete: the intake checklist and routing rules. The live pilot is in progress; the timing review is next. I’ve linked the team’s recorded work to each milestone and kept the original goal in view.

Saved context retrieved: Job assignment turnaround · The approved plan, recorded milestone completions, pilot work, and the one-business-day target.
Still unknown: The completed pilot and timing review are still needed to verify the assignment-time goal.

What I can take on next

I’d like to bring you a concise progress report with the pilot’s blockers, responsible people, and a recovery option for anything that puts the target date at risk.

Everyday requests. Separate chats.

The shared state is the handoff

Chat 1 of 3

YOU ASK IN A NEW CHAT

The starting point

“I’m covering dispatch today. What needs doing?”

Illustrative answer

Two pickups need drivers, and the next job is waiting on a supplier delivery time. Your Operations dispatch role gives you the current shared queue, including completed work and open blockers.

Sources and saved context: Shared job state · Department task queue · Recorded approvals · Your existing role and access
Still unknown: The supplier’s delivery time and one driver’s availability still need confirmation.

What I can take on next

I can prepare the driver assignments from the current queue and identify the one confirmation needed to finish the dispatch plan. The shared records already carry the handoff.

YOU ASK IN A NEW CHAT

From the dispatch queue during the shift

“Delivery is confirmed for 10. The driver is available. Assign the pickups.”

Illustrative answer

The jobs now show the confirmed 10 a.m. delivery, and the pickups are assigned within your dispatch authority. Those changes are recorded in the shared state as part of the work.

Saved context retrieved: Operations dispatch queue · The existing job queue, your supplier and driver confirmations, and the recorded dispatch assignments.
Still unknown: A confirmed delivery time is not yet evidence that the materials have arrived.

What I can take on next

I can bring the affected jobs and next assignments into a current readiness view. The next authorized coordinator will see these updates when they ask.

YOU ASK IN A NEW CHAT

The next shift, the regular dispatcher

“I’m back on dispatch. What needs my attention?”

Illustrative answer

The pickups have assigned drivers, and the materials delivery is scheduled for 10 a.m. Arrival is not yet recorded. Your existing dispatch role gives you the current job state without a separate handoff note or the covering employee’s chat.

Saved context retrieved: Operations dispatch queue · The shared updates from the previous shift, current job records, and equivalent departmental access.
Still unknown: Delivery arrival has not yet been recorded in the connected job source.

What I can take on next

I can check the connected job and delivery records, update your working queue, and bring forward only what still needs attention.

Everyday requests. Separate chats.

A request keeps its approval boundary

Chat 1 of 3

YOU ASK IN A NEW CHAT

With the payment selected

“Can I approve this refund?”

Illustrative answer

You can prepare the request; the location manager must approve it. I’ve linked the open refund issue to the selected payment, PAY-1042, with its approval rule and missing details.

Sources and saved context: Payment record · Refund policy · User and agent permissions
Still unknown: The refund reason and supporting details are incomplete.

What I can take on next

I can prepare the request for the authorized manager with the missing information clearly identified.

YOU ASK IN A NEW CHAT

With the duplicate-payment records attached

“The charge was duplicated. Prepare the refund request.”

Illustrative answer

The request includes the duplicate-charge reason and supporting payment records. It remains a request for the location manager, not an issued refund.

Saved context retrieved: PAY-1042 refund issue · The payment context, completed reason, supporting records, and manager approval rule.
Still unknown: Manager approval has not been recorded.

What I can take on next

I can prepare the review package for the authorized manager.

YOU ASK IN A NEW CHAT

When checking progress

“Has that duplicate-charge refund gone through?”

Illustrative answer

I found the refund request linked to PAY-1042. It is prepared, but neither manager approval nor a payment-system confirmation is recorded. I can’t yet confirm that the refund went through.

Saved context retrieved: PAY-1042 refund issue · The prepared request and the separate approval and execution states.
Still unknown: Issuance requires an authoritative payment record; its absence here is not proof no payment occurred.

What I can take on next

I can show the known status and check the permitted payment source for confirmation.

Illustrative scenarios, not live customer results. This is the experience we’re building toward. Useful answers depend on source coverage, freshness, and permissions; an action still follows its approval rules.

Less uncertainty in the way you work

The answers should get better
as your context grows.

Get to the finished work faster.

Once your templates, client information, and instructions are connected, ask for the document you need. AI can fill it out from that context, without uploading the same template or explaining the client again.

Know what supports an answer.

Connect conclusions to sources. See what is current, what conflicts, and what still needs to be established.

Let AI carry the context forward.

As you work, agents should update the canon within their roles and permissions—or bring the change to you when it needs discussion.

We call that maintained, authoritative context your canon. Canonicalization is the work of establishing it and keeping it aligned with reality.

Business Control

See what your Canon understands.
Control where it goes next.

Business Control is the visual representation of your business Canon — a dashboard maintained and updated through your agent or agents.

A business Canon can begin from existing records, owner knowledge, operating systems, or connected personal and team context. As that understanding grows, its structure, decisions, dependencies, priorities, and current state become increasingly dynamic. At that point, understanding the whole business through prompts alone becomes difficult.

Business Control gives that understanding a place to live visually.

Instead of asking your agent to reconstruct the state of the business every time you need context, you can see the Canon’s current understanding: what is known, what is changing, what remains unresolved, where the business is heading, and what needs attention next.

Your agents continue to work through the Canon. Business Control turns that work into an understandable operating view — giving you a quick place to understand your business, then use your agents to investigate, decide, change, and act.

The Canonis the understanding.

Your agentswork with that understanding.

Business Controllets you see and direct it.

The foundation of Business Control

A clearer business.
A more confident owner.

A good budget gives you room to breathe: you know where you stand and what your choices mean. ForwardCanon applies that discipline to the whole business—demand, resources, decisions, and results.

Demand
What do customers pay for, and which revenue streams bring money into your business?
Map the revenue streams behind actual customer purchases.
Supply
What people, resources, costs, and capacity support that demand?
Understand the operating commitments.
Supply Optimization
What should change to create a healthier, sustainable business?
Compare configurations, risks, and expected results.
Profit Management
How should proven profit protect and strengthen the business?
Build resilience, longevity, and future opportunity.

This is how we work toward business health.

Business Control and shared business operation follow these four layers.

Projected improvements carry assumptions and supported uncertainty. Actual results validate them.

Profit Management begins with demonstrated surplus. The model keeps evolving as reality changes.

Business Control is being developed through real implementations. The view depends on the sources, freshness, and permissions established for your business.

Clarity creates freedom

Build confidence you can carry forward.

The goal is for you to ask high-level questions, understand the evidence behind the answer, and make your own decisions with greater confidence. As your relationship with AI develops, everyday clarity should require less dependence on us.

Simple starting prices

Choose how much
you want to take on.

Start through conversation. Add Business Control when you want the business model, and an engineer when you want help establishing and maintaining it.

Individual & team

Maintain your Canon.

$15/seat/month

Shared Canon: +$50 per workspace/month

Personal continuity and self-managed shared work, with documented structures you can make your own.

Personal Canon for each participant
Team context with defined roles and access
Documentation and agent-guided setup

Start here

Business Control

See and direct your business.

$299/business/month

Plus $15 per seat/month

Maintain the business model yourself through your agents and its visual operating view.

Demand and Supply
Supply Optimization and Profit Management
Decisions, dependencies, and current state

Start here

Business Engineer

Build it with an engineer.

$1,000/month

Plus an estimated one-time setup fee

A defined engagement to establish and maintain Business Control with you.

Business Control platform included
Setup quoted by scope and estimated time
Monthly time allowance agreed in advance

Connect with a Business Engineer

A clear decision to keep the engineer. Your proposal defines setup deliverables, estimated time, and the monthly time allowance. Additional work is agreed separately. You can continue maintaining Business Control yourself at its platform price when the engineer engagement ends.

Shared Canon is a separate $50/month charge per shared team workspace, plus seats. Add it independently or alongside Business Control. Engineer pricing includes the Business Control platform; seats and Shared Canon are additional. Five seats with Shared Canon are $125/month; with self-managed Business Control, $424/month. Prices are in USD. Self-service accounts, agent connections, trial activation, and checkout are in development; these are our starting prices.

What would you like to stop guessing about?

Tell us where context breaks down or which decisions feel harder than they should. We’ll discuss a practical starting point.

Start here Connect with a Business Engineer

Start with the authoritative realitythat already exists.

For you

For your business

For your team

Your agent helpsyou get established.

Create your account.

Talk it through with your agent.

Review your first Canon.

Put it to work.

What prompting with Canon looks like

“What does my workday look like today?”

“Help me keep my workweek organized.”

“What does my week look like?”

“Where is our customer money coming from?”

“Which services are worth growing?”

“Can our team handle more repeat-service work?”

“What did Timmy get done last week?”

“What’s blocking Timmy, and can we help?”

“How did Timmy get on this week?”

The answers should get betteras your context grows.

Get to the finished work faster.

Know what supports an answer.

Let AI carry the context forward.

See what your Canon understands.Control where it goes next.

A clearer business.A more confident owner.

Demand

Supply

Supply Optimization

Profit Management

This is how we work toward business health.

Build confidence you can carry forward.

Choose how muchyou want to take on.

Maintain your Canon.

See and direct your business.

Build it with an engineer.

What would you like to stop guessing about?

Start with the authoritative reality
that already exists.

Your agent helps
you get established.

The answers should get better
as your context grows.

See what your Canon understands.
Control where it goes next.

A clearer business.
A more confident owner.

Choose how much
you want to take on.