What the assistant can do
The bluprnts assistant can add and edit products, sales, employees, costs, financing, projects and company settings — every change confirmed by you, and undoable.
The assistant doesn't only answer — it can build your model. Describe what your business does and it proposes the entries to match, batched into a single confirmation.
What it can change#
| Domain | What it can add or edit |
|---|---|
| Products | Name, type, price, unit costs, VAT applicability, billing period |
| Sales | Volume, price, dates, the product being sold |
| Employees | Role, pay, on-costs, start and end dates |
| Costs | Amount, type, timing |
| Financing | Loans and investment |
| Projects | A project layer and what goes in it |
| Company settings | Tax rates, VAT, payment terms and the rest of your company options |
These are the same objects you would create by hand, saved the same way, through the same authorised endpoints. Nothing the assistant makes is a special kind of record.
The confirmation step#
When it wants to change something, you get a card listing the batch:
Apply 3 changes?
Each row shows what it would do, a summary, and the specific values — a rate, a date, an amount — so you can check the numbers before they land rather than after.
- Confirm applies the whole batch.
- Discard throws it away entirely.
There is no way for the assistant to write to your model without passing through this card.
Undo#
Confirmed changes appear in the Changes panel down the side, most recent first. Each one shows its domain and what it did; selecting it expands the detail.
- Undo reverses that one change.
- Undo all reverses everything applied in the session.
Every applied action knows how to reverse itself, which is why undo is offered per change rather than as a single "back" step.
Working with it well#
Describe the business, in a batch. "We're a coffee roaster. We sell 1kg retail bags at £24 that cost £9 to make, about 400 a month, and wholesale at £16 with 200 a month. Two roasters on £32k, rent £1,800 a month." — one message like that produces a substantial model you then check and confirm.
Check the values, not just the labels. The confirm card exists so you read the figures. An assistant that mishears £32k as £3.2k produces a plausible-looking employee and a wrong forecast.
Fix by asking. "Make the wholesale price £18" edits the existing sale rather than creating a second one.
Related#
- Ask about your forecast — questions rather than changes.
- Limits and guardrails — what it won't do.
- How forecasts are built — what it's building, and why the drivers matter.