Business OS / How it works

[ 05 . STAGES . LIVE ]

From application to a working book of business, in five stages.

The work that runs behind your brand is built to wear it. This page walks the path. You apply, we provision your partner workspace, you set up your brand kit once, you onboard accounts that live inside their own isolation boundary, and the model operates under your name. You decide the price, you keep the spread.

Three brands in the chain · One engine room

Larasengine roomPartneryour brand on topBusiness owneryour customerEnd customertheirs

The shape of it

One partner workspace, many accounts, your brand on top.

Your partner workspace is the shell. Inside it, you provision one account per business owner. Each one is sealed from every other at the row level. The brand kit you set once stamps every surface. The model runs under your name, serves the business owner, and talks to their end customers in the channels they already use.

partner workspace

stages, end to end

0 days

to first account live

Stages / 05partner workflow

Day zero

You apply, we review, you get a partner workspace under your name.

Apply to the partner program. We review every application by hand. Once approved, your partner workspace is provisioned and locked to your account, your seat structure, and your billing posture.

Who acts

You. The partner principal who will run the book of business.

Surface

Partner console. The shell that wraps every business owner account you spin up after.

Output

A live workspace, your partner record on file, and a runway to brand setup. No business owner data yet, no AI work running yet.

Application

A short form. Who you are, what you sell, who you sell to. We read every line.

Review

A human reads the application. We accept partners we believe will run a clean book.

Provisioning

Partner workspace stood up with your principal seat, your billing rail, and your isolation boundary.

Welcome

A short call or thread to align on the first business owner you will onboard and the brand kit you want to ship.

Brand setup

A few hours

Your brand kit goes in once, every surface picks it up.

Logo, color, typography, domain, sender, voice. The brand kit lives in the partner console and stamps every business owner surface from the sign in screen to the reply that goes out overnight, every night.

Who acts

You, or a designer on your team. One setup pass, the whole book of business inherits it.

Surface

Brand kit in the partner console. Your brand on every surface, no Laras name on anything customer-facing.

Output

A signed brand profile. The next account you provision opens already wearing your colors and speaking in the voice you set.

Identity

Logo, mark, color tokens, type pair. Applied to the business owner dashboard and every export.

Domain

Custom domain for the business owner sign in, the webchat embed, and the report links.

Sender

Email sender and signature. Voice line greeting. WhatsApp display name where the rails allow.

Voice

Tone preset. Warm, formal, technical, playful. Per account override available, your default sets the bar.

Pricing posture

Subscription, retainer, project, outcome. You pick the model, the math is yours to keep.

Business owner onboarding

Under an hour per account

Your business owner signs in to your engine room, not ours.

You provision a workspace from the partner console. The business owner signs in at your domain, sees your brand on every screen, and walks through an onboarding flow you tuned. Their catalog, policies, and channels land in their isolation boundary.

Who acts

The business owner, with your team available as a shadow co pilot for the first week.

Surface

Business owner workspace. Their own walled-off account, separated from every other one on your book.

Output

A workspace with catalog, policies, channels, and grounding wired up. Ready for the AI to start working under approved rules.

Provision

Spin up a new workspace in minutes. Their own per-workspace isolation from second one.

Catalog import

Products, pricing, FAQ, and policies imported or pasted in. The knowledge layer reads from your books, not its memory.

Channel connect

Instagram, WhatsApp, Facebook, webchat, email, voice line. Each channel authorized by the business owner, not by you.

Rules of engagement

Approval thresholds, business hours, escalation paths. The business owner sets them, you can recommend defaults.

Shadow co pilot

You can shadow into the account to assist without touching billing or auth. The business owner sees that you joined.

The model runs the work

Continuous

The model answers, schedules, reports. Under your brand, inside their rules.

Inbound messages and calls land. The model reads them against the catalog and policies, drafts a move, runs it through the truth firewall, and either sends or stages for review. Every move logs, every outcome closes the loop.

Who acts

The model. The business owner team supervising, you watching the book of business from the partner console.

Surface

Chat desk, voice line, sales sequences, knowledge layer, CRM, control rails. One surface across all of it, shared memory underneath.

Output

Replies sent, calls handled, meetings booked, payments confirmed, reports delivered. All under your brand. All logged.

Signal

A DM, a comment, an inbound call, a webform lead, a webhook from a connected rail. Anything that needs a response.

Grounding

The knowledge layer pulls the relevant catalog facts, pricing rules, policies, and prior thread context.

Draft

The model drafts a reply, a call script, a sequence, an action. Tone, grounding, and rules baked into the draft.

Firewall

Unsupported claims rewrite or hold. The truth firewall blocks hallucinations before the end customer sees them.

Send or stage

Safe work runs automatically. Risky moves stage in the approval queue with a clear reason and recommended action.

Close the loop

Outcome tagged, audit log written, business owner report updated. The 24 hour mark closes the move for good.

You earn

Every cycle

Business owner pays you, you pay your tier, the spread is yours.

You charge the business owner on the model you set. Subscription, retainer, project, outcome. You pay your partner tier to Laras for the underlying capacity. The difference is your margin. The book of business reports up to one screen in the partner console.

Who acts

You. The business owner sees only your name on the invoice.

Surface

Partner console. Book level reporting, usage by account, renewal posture, margin trail.

Output

Recurring revenue under your brand. Predictable cost from the tier you sit on. A growing book of accounts that compound.

Owner billing

You bill the business owner on your terms. Laras does not touch the relationship or the money path.

Partner tier

You sit on the partner tier that fits your book. Move up or down as your volume changes.

Book reporting

One screen across every account. Usage, outcomes, renewal posture, escalations that need your attention.

New owner

Provision the next account in minutes. The brand kit, the pricing posture, the rules carry over.

Control rails, always on

Autonomy on safe lanes, approval where it matters.

The model does not ask for permission on every move. Safe replies inside business owner rules run automatically. The approval queue catches the few moves that need a human. The audit log writes every decision with the data behind it. You keep the final say without being on call.

Truth firewall

Unsupported claims rewrite or hold. Hallucinations never reach the end customer.

Auto safe lanes

Low risk work runs. The queue stays short on purpose so the business owner actually reviews it.

Approval queue

Price, refund, policy, and brand sensitive moves stage with a reason and a recommended action.

Audit trail

Every move logged. Model, input, gate decision, outcome at the 24 hour mark.

Start the workflow

Your brand on top. Laras underneath.

Partners go from application to a provisioned workspace, a wired brand kit, and a first account live inside a single week. Sign up when you are ready. We review every application by hand.