Skip to content

Customer stories

See how a business would run on BusinessIntents, one workflow at a time.

Three representative scenarios follow documented workflows from the first record to the posted ledger entry: connected operations, a sales workflow, and finance control.

Each scenario names the roles involved, the records that change, the setup it needs, and the limits of the current product.

Questions about the scenarios, or interested in sharing your own experience? Write to office@codbex.com.

Connected operationsSalesFinance controlDocumented workflowsEnglish and Bulgarian

How to read these pages

Real product behavior, representative companies.

Every step in the scenarios links to a workflow guide that describes the actual screens, statuses, and automatic actions in BusinessIntents. The companies themselves are generic: they help you picture the product in a business like yours, without presenting invented customers, quotations, or figures as evidence.

Scenarios

Choose the scenario closest to your business.

Each one can be read on its own and links to the detailed workflows.

01

Connected operations

A small distributor moves one order from sales through the warehouse, invoicing, payment, and the ledger without re-typing it.

Read the scenario
02

Sales workflow

A small B2B sales team takes a deal from first contact through quotation, order, and invoice to payment and reminders.

Read the scenario
03

Finance control

A finance team puts approvals, separate payment duties, and an immutable ledger behind purchases, expenses, and corrections.

Read the scenario

What each scenario contains

The same parts in every scenario, so they are easy to compare.

Every scenario is written to the same structure.

01

The starting point

The typical process before BusinessIntents and where it breaks down.

02

The documented workflow

Six steps, each linked to the guide with its roles, statuses, and refusals.

03

Setup and limits

What must be configured before go-live, and what the product does not automate yet.

Published customer stories

How a named customer story is published.

Named case studies will appear here only when a customer agrees to share its experience. These rules apply to every story.

Written permission

A customer's name, logo, quotations, screenshots, and figures are published only with the customer's written permission.

Customer review

The customer reviews and approves the final text, in every language it is published in, before it goes live.

Figures with a source

Results are stated only with the period, the measurement method, and the customer's own data behind them.

Updates and withdrawal

A customer can ask for its story to be corrected or removed at any time by writing to office@codbex.com.

Continue the evaluation

Continue from the scenarios to the product.

The scenarios draw on these pages. Use them to check the details.

Decision-stage questions

Questions about customer stories.

Are these real customers?

No. They are representative scenarios. The workflows are real and documented; the companies, their starting points, and their teams are generic.

Why are there no named case studies yet?

A case study is published only when a customer has approved every detail. Until then, the scenarios show the product's documented behavior without borrowing anyone's name.

Can we become a published customer story?

Yes. Write to office@codbex.com. The story is prepared together with you and published only after your written approval.

How can we check a scenario against our own process?

Start the Free Demo, which has no time limit and fewer features than paid access, or ask the team to walk through the workflows with you in English or Bulgarian.

Next step

Find the scenario that looks like your business, then try it.

Open the free demo, or ask the team to walk through a scenario with your own process in mind.

Questions about the scenarios, or interested in sharing your own experience? Write to office@codbex.com.

The BusinessIntents Business Suite - end-user guide.