How it works

One workflow to start.
Built around your team.

Start with one part of your business. We configure LBOS around that process, agree which tools stay, and test the setup with your team before launch.

Discuss your first workflow See the process

01 / Choose the workflow

Start with the work.
Make the first step clear.

A new inquiry, a document request, an appointment follow-up. Choose one recurring process and walk us through how your team handles it today.

  • What starts the work?
  • Where does your team lose time?
  • What would a useful result look like?
Before we build

We agree the first scope, delivery timeline, pricing, and support.

Your first workflowExample brief

Client onboarding

“We spend too much time chasing the documents we need to get started.”

Starts with
A new client inquiry
What’s needed
Business details, accounts, and statements
A useful first result
A complete file, ready for the team to review
One process. A clear place to begin.

02 / Set up the connections

Your tools.
Your rules for the work.

We map the information the workflow needs, check tool access, and agree who reviews each important step. If a custom connection is needed, we assess its requirements and scope before building.

  • Confirm access and the information to share
  • Decide what LBOS prepares or carries out
  • Give exceptions a person and a next step
What we define together

We configure and test the agreed setup. Your team provides examples, authorizes access, and reviews the results.

Illustrative onboarding setup

Your inboxThe conversation
Your documentsThe information
LBOS prepares the workClient context + proposed next step
Your team reviewsBefore an agreed approval step proceeds

Connections are confirmed for your tools and process.

03 / Test it together

Try the usual path.
Then the unexpected.

Check the outputs and handoffs with your team. A missing document or unusual request should lead to a useful next step, not leave someone guessing.

Try both situations in this example.
Watch how the next step changes.

What your team checks

The information is right, reviews happen where they should, and exceptions have a clear route.

Workflow testIllustrative example
Try a different situation
MC
Maya ChenClient onboarding · Example request
  1. 1Read the requestNext
  2. 2Check the documentsNext
  3. 3Prepare the next stepNext

Choose a case, then run the example.

No messages are sent.

04 / Launch, then improve

Put the first workflow
to work.

Agree what’s ready, who owns it, and how your team gets help. Then review the results and make adjustments before deciding what to connect next.

Expand when it’s useful

Add the next workflow when the first is ready.

What we review before launch

Ready for your team?

  • The first workflow has a clear scope
  • Your team has reviewed the test results
  • Approvals and exceptions have an owner
  • Support contact and maintenance responsibilities are agreed
LaunchReviewImprove

For the first conversation

You know the work.
Start there.

You don’t need a technical brief.
Just bring a process your team knows well.

  1. One example of the workAn inquiry, request, or follow-up that takes too much effort.
  2. The tools you use todayWhere the conversations, records, and documents live.
  3. The people involvedWho does the work, who reviews it, and who handles exceptions.

Before we begin

A few practical
questions.

What should we bring to the first conversation?

One recurring process, the tools your team uses, and an example of where the work gets stuck. You don’t need a technical specification. A simple description of how things happen today is enough to start.

How long does setup take?

Timing depends on the workflow, the connections, and the reviews it needs. We agree a delivery scope and timeline after understanding the work, before implementation begins.

When do we discuss pricing?

Once the first workflow and its requirements are clear. We agree scope, pricing, and support before building, so you can decide whether the proposed setup makes sense for your business.

Do we have to move everything into LBOS?

A complete move is not assumed. We agree which tools stay, what information needs to connect, and whether any records need to be brought into LBOS. Access, data preparation, custom connections, and any change to the way your team works are part of the scope.

Who looks after the setup once it is live?

Before launch, we agree who your team contacts for help, who is responsible for maintaining the connections, and how issues or changes are handled. The included support, ongoing responsibilities, and any additional work are defined in your agreed scope.

What if something needs a person?

We include those situations in the design and testing. Missing information, unusual requests, and actions that need approval should have a clear next step for your team.

Let’s find your starting point

Which process needs
less chasing?

Tell us what happens today and what you’d like to improve.

Discuss your first workflow Explore the product