Business Execution OS
← Back to Bexos

02 / Implementation — the systems layer

Connected work.
Lasting systems.

Ten ways to put operational AI to work in a founder-led company.

Architecture and design establish the information, responsibilities, and connections. Implementation makes them work together. Training brings the team into daily use and improvement. Explore each example below.

The examples throughout run on three operating shapes: a 42-person field-service company across three regions, an 85-property management portfolio, and a distributor with two warehouses and three sales channels.

01

Customer follow-through

Every open conversation.
A clear next step.

Requests arrive through email, forms, and customer records. A follow-through system brings the relevant history together, identifies what is still open, and prepares the work needed to move it forward.

Explore this system

In the businessA shared queue gives the team a place to review inquiries, check commitments, and take over with the conversation already in context.

Over timeNew replies update the record. Completed work leaves the queue. Duplicate requests are recognized, and items waiting too long come back into view.

Checked againstpast requests with known outcomes: which were genuinely open, which were duplicates, which were already answered elsewhere. A request wrongly closed is the failure that matters, so that is the one counted.

A person decideswhether a prepared reply is sent. The system assembles the context and drafts; it does not answer a customer on its own.

Connects tothe shared inbox, the customer record, and the calendar, so a commitment made in an email and one made in a meeting reach the same queue.

FIELD SERVICES / FOLLOW-THROUGHWorked example · prewritten

Follow one request

Select a stage to follow the work.

02

Team knowledge

Business knowledge.
Within reach.

Give procedures, product information, and troubleshooting guidance a useful front door. The assistant finds relevant information, shows where it came from, and identifies the questions that need someone’s attention.

Explore this system
01 / Maintain

The source library

Procedures, business records, and guidance with a responsible team member and a review date.

02 / Retrieve

The relevant context

Information selected for the question and the person asking it.

03 / Use

An answer and a next step

A source to inspect, or a clear route to resolve missing information.

Checked againsta question set written with the team, including questions the library should not be able to answer. An assistant that answers everything is not passing — it is guessing.

A person decideswhat enters the source library, and who owns each document with a review date attached. Unowned knowledge goes stale invisibly.

Connects tothe document store, the procedures already written, and the support history, so an answer can cite the passage it came from rather than paraphrasing from memory.

As procedures change, the source library and test questions change with them. Questions the system cannot answer help reveal what the business needs to document next.

Try the property-management example ↗
03

Document preparation

From scattered files
to a reviewable picture.

Bring forms, correspondence, and supporting documents into a structured record. Extract the relevant facts, compare information across files, and prepare a packet with sources and unresolved questions.

Explore this system

In the businessUseful for supplier onboarding, project intake, and assembling the information behind a business decision.

Over timeNew documents join the same record. Missing items and conflicting details remain visible until resolved, with a history of revisions.

Checked againstdocuments with deliberate conflicts and omissions seeded into them. The system passes when it surfaces the conflict and names both sources, not when it picks one.

A person decidesevery unresolved question before the packet moves. A conflict is routed, never silently resolved.

Connects tothe file store, the supplier or project record, and the approval path the business already uses.

SUPPLIER ONBOARDING / REVIEW PACKETWorked example · prewritten

Example Supply Co.

One item to resolve

Information assembled

Business name
Example Supply Co.Supplier form · section 1
Primary contact
Jordan LeeSupplier form · section 2
Delivery region
North districtService overview · page 2

Review before approval

The form lists a 5-day lead time. The service overview lists 7 days. Which should purchasing use?

Inspect the conflicting sources

Supplier form, section 3: “Standard lead time: 5 business days.”

Service overview, page 2: “Allow 7 business days for standard delivery.”

Assigned to purchasing · clarification needed

Supporting documents → structured record → review questions → decision packet
04

Operational visibility

A useful brief.
Ready for the day.

Bring changes from your business systems into a recurring brief: what moved, what is waiting, and which decisions need attention. Each item connects back to a record the team can inspect.

Explore this system

In the businessCombine open customer requests, delivery exceptions, and team actions into a practical management view.

Over timeTrack what has already been reported, refresh changed items, and show when a source could not be updated. A quiet system should still be an inspectable one.

Checked againstits own freshness. Every source carries a last-successful update, and a brief that cannot confirm a source says so in the brief. A quiet morning and a broken connection must never look the same.

A person decideswhat counts as an exception worth surfacing. That threshold is set with the team and revisited, because a brief that reports everything is one nobody reads.

Connects tothe scheduling, customer and delivery systems, read-only, with the connection history visible on the page.

FIELD SERVICES / MORNING BRIEFWorked example · prewritten

Three things to look at.

Prepared at 8:30 a.m. / Sample day

CUSTOMERS A service proposal is waiting on site details.

Alex has prepared the questions. Confirm access hours and the site contact before completing the proposal.

Source: inquiry JS-104 · next action assigned to Alex

DELIVERY A supplier’s lead time needs clarification.

The onboarding form and service overview disagree. Purchasing has the two source passages and an open clarification task.

Source: Example supplier packet · unresolved question 01

INFORMATION The scheduling source has not refreshed.

The last successful update was yesterday at 4:00 p.m. Check the scheduling system for today’s changes before using those records.

Source: connection history · latest refresh incomplete

05

Meeting follow-through

Turn the discussion
into work that moves.

Turn meeting records into decisions, accepted actions, deadlines, and draft follow-ups. Keep open questions visible and carry outstanding work into the next review.

Drawn from implemented meeting records and action registers for a business I’m involved in.

Explore this system

In the businessA shared action register preserves who agreed to do what, while keeping suggestions separate from commitments.

Over timeReview progress against the previous meeting, capture changes to deadlines, and retain the discussion behind a decision.

Checked againstrecords where a decision was reversed later in the conversation, or where a suggestion was never accepted. The system passes when those do not appear as commitments.

A person decideswhich draft follow-ups are sent, and whether a suggested next step becomes an assigned one.

Connects tothe meeting record, the action register, and the calendar for deadlines.

Worked example · prewritten output

Meeting excerpt

“Let’s test the new welcome email across three account teams. Maya, can you draft it by Thursday?”

“Yes. Should we add a discount?”

“Let’s decide that after we review the draft.”

Action register

Decided

Test a new welcome email across three account teams.

Accepted action

Maya → draft email
Due Thursday

Open question

Include a discount? No decision yet.

Read the draft follow-up For review · unsent

Hi team — we agreed to test the welcome email across three account teams. Maya will draft it by Thursday. Whether to include a discount is still open and will be discussed after draft review.

Suggested next step, not an accepted commitment: assign someone to review Maya’s draft.

06

Content production

Your voice.
A repeatable process.

Connect research, writing, production planning, and publishing preparation. Carry your voice, source material, and review standards across stages and languages.

Based on an implemented four-stage workflow for bilingual content production.

Explore this system

In the businessMove from a topic and source brief to scripts, production instructions, and a package ready for editorial review.

Over timeApproved examples and feedback strengthen the working reference. Versioned briefs keep changes traceable across English and Spanish.

Checked againstan approved reference set of work already published and accepted. New output is compared against it for voice and for the claims it makes, and a claim with no source in the brief blocks the stage.

A person decidespublication, always. Every stage before it is preparation.

Connects tothe source material, the working style reference, and the publishing tool, with versioned briefs so a change stays traceable across languages.

Worked example · prewritten
ResearchWritingProductionReview

A better customer welcome

View the sample research brief

Question: what should a first welcome email include? Source: the company’s onboarding checklist, §1 — “Explain the next step, link to the getting-started guide, and name a support contact.” Editorial direction: practical, conversational, with one clear example. No performance claims.

Script excerpt / English

“Your first email should answer the customer’s first question: what happens next? Start with one clear next step, a useful link, and a real person they can contact.”

Topic → source brief → scripts → shot list → publishing package.
Human review before publication.

07

Proposal & scope preparation

From the first conversation
to a considered proposal.

Connect discovery notes, customer requirements, approved service descriptions, and pricing rules. Prepare a scope that reflects the request, with the assumptions and unanswered questions ready for review.

Explore this system

In the businessGive the sales and delivery teams a shared starting point: what the customer needs, what is included, and what must be confirmed before quoting.

Over timeRevisions stay attached to the opportunity. Approved changes update the scope, and the final agreement becomes the starting point for delivery rather than another round of re-entry.

Checked againstpast opportunities where the scope changed after signing. The system passes when it raises the assumption that later proved wrong — as an open question, not as an answer.

A person decidesthe scope and the fee, without exception. The system prepares a starting point; it never quotes.

Connects todiscovery notes, the approved service descriptions, and the opportunity record, so a revision stays attached to the opportunity instead of becoming a new document.

FIELD SERVICES / PROPOSAL WORKSPACEWorked example · prewritten

Regional maintenance expansion

Discovery → requirements → proposed scope → review

What the customer asked for

“We need routine maintenance at eight additional sites, with visits before opening. We’d also like an option for weekend callouts.”

Source: discovery notes · request 04

Prepared for the proposal

INCLUDED

Routine maintenance visits before opening, using the agreed site checklist.

OPTION

Weekend callout coverage, priced separately against the approved service schedule.

TO CONFIRM

Access window, visit frequency, and weekend response expectations.

See the scope review

The request asks for weekend callouts but does not specify a response time. Confirm the service expectation before including a response commitment or calculating the option fee.

Source check: discovery notes, request 04; service catalog, maintenance and callout sections. The proposal remains attached to these references as it is revised.

08

Customer-feedback intelligence

Hear the pattern
behind the messages.

Bring support conversations, reviews, and survey responses together. Group the recurring themes, preserve the customer’s words, and turn repeated friction into a focused improvement list.

Explore this system

In the businessGive service, product, and operations teams a common view of what customers are struggling with, supported by messages they can inspect.

Over timeTrack themes across comparable periods, remove duplicate conversations, and review whether a change addresses the original issue. New themes can enter the classification as the business evolves.

Checked againsta hand-labelled sample. Agreement with the human labels is measured, and the disagreements are read rather than counted, because that is usually where a new theme is hiding.

A person decideswhich themes become work. The system groups and evidences; prioritising is a business judgment.

Connects tosupport conversations, reviews, and survey responses, keeping the customer's own words attached to every theme so a conclusion can be checked against the message that produced it.

09

Market & supplier monitoring

Keep up with
what actually changed.

Watch selected supplier announcements, product pages, market sources, and competitor offerings. Compare each update with the previous record and prepare a short brief explaining what changed and why it may matter to your business.

Explore this system

In the businessHelp purchasing, sales, and the leadership team spot a changed lead time, a discontinued product, or a new alternative without repeatedly checking the same pages.

Over timeKeep dated snapshots and a history of findings. Previously reported changes stay out of the next brief unless they change again, and unavailable sources are visible.

Checked againstits own diff. Snapshots are dated and retained, a previously reported change does not report twice unless it changes again, and a source that could not be reached is named as unreachable rather than treated as unchanged.

A person decideswhether a change matters. The system is deliberately conservative about significance; a small wording change and a discontinued product both surface, and a person triages.

Connects tothe supplier and product pages being watched, and the purchasing record they inform.

DISTRIBUTION / CHANGE WATCHWorked example · prewritten

A supplier update worth reviewing.

PREVIOUS SNAPSHOT

Standard dispatch: 3 days

Supplier product bulletin · revision A

LATEST SNAPSHOT

Standard dispatch: 7 days

Supplier product bulletin · revision B

What this affects

Check delivery promises on open proposals that depend on this supplier. Ask purchasing whether an alternative source is available for time-sensitive orders.

Inspect the change record

Revision A: “Standard dispatch within 3 business days.” Revision B: “Standard dispatch within 7 business days.” Both excerpts refer to the same product range.

Next review: purchasing confirms the impact. The changed wording is retained alongside the previous snapshot for future comparison.

10

Sales-performance analysis

Ask a better question
of your business numbers.

Connect order, customer, and product data to a repeatable analysis process. Explore changes in sales, order value, and customer activity, with clear definitions and a path back to the underlying records.

Explore this system

In the businessMove from a broad question such as “How are sales doing?” to a useful comparison by period, product, channel, or customer group.

Over timeRefresh the same definitions as new data arrives. Keep saved views and comparison periods consistent so a change in calculation does not masquerade as a change in the business.

Checked againstthe definitions, not only the figures. Every reported number reconciles to the source record, and a reconciliation that fails stops the report rather than footnoting it.

A person decideswhat the numbers mean. The system states what moved and against which record; the interpretation is a conversation.

Connects tothe order and accounting systems, read-only, with each figure traceable to the record it came from.

DISTRIBUTION / SALES EXPLORERWorked example · prewritten

Sales rose. Order volume fell.

Two equal 30-day periods · two warehouses · three sales channels

NET PRODUCT SALES$624,000

Previous: $600,000 +4%

COMPLETED ORDERS480

Previous: 600 −20%

AVERAGE ORDER VALUE$1,300

Previous: $1,000 +30%

The next question

Higher average order value more than offset the lower order count. Break the change down by new and returning customers, then by product mix, to understand what drove it.

Inspect the calculation and definitions

Previous period: $600,000 ÷ 600 completed orders = $1,000 per order. Current period: $624,000 ÷ 480 = $1,300 per order. Sales change: ($624,000 − $600,000) ÷ $600,000 = 4%.

Net product sales exclude tax and shipping and include product returns attributed to those orders. Cancelled orders are excluded. The same definitions apply to both periods.

Architecture and design / Built for ongoing work

The work continues.
The system should too.

A useful system needs more than a good first result. I design for the information, people, and tools that will change around it.

Information that carries forward.

Keep business records in an explicit store, with source links, history, and a practical export path.

Connections you can inspect.

Make integrations, processing status, and exceptions visible so a missed update can be found and addressed.

Changes you can evaluate.

Use representative examples to check revisions to instructions, sources, tools, and models before relying on them.

A plan for the next chapter.

Document configuration and responsibilities. Consider migration and maintenance as part of the scope from the beginning.

A 45-minute conversation

What should work
better next?

Bring a priority, an unfinished experiment, or a question about how AI fits your operation. I’ll help you connect it to a useful first step, from the foundation through to the team using it.

No preparation is required. If it helps, bring an example of something you want to improve, anything you have already tried, and who would use the result.

Book a 45-minute conversation