Case study · Ubees
Proposal work fell from thirty hours a week to five.
After an €8M Series A, Ubees needed its sales process to scale without asking experienced people to spend another day moving figures from Sheets into slides.
Growth had turned proposals into a bottleneck
Each proposal combined prospect, crop, region and programme parameters, then moved the right figures into a presentation. The task repeated, but experienced people still owned it because they knew the sources and exceptions.
At thirty hours a week, this was no longer a convenience issue. A meaningful part of sales capacity disappeared before the final conversation and decision.
Building proposals took about thirty hours every week. The work was repeatable, but the knowledge inside it belonged to experienced people.
Before
Thirty hours of senior time every week.
What Basalt built
Basalt turned the repeatable proposal work into a structured production workflow while keeping review and final decisions with the team.
After
Five hours for the same recurring proposal workload.
Key figures
30 → 5 h
per week
The same proposal workload before and after.
≈1,300 h
returned each year
Annual scale derived from 25 hours returned each week.
02
Automate assembly, retain judgement
The application reads the three Sheets used by the team and prepares recurring parts from the chosen parameters. It removes searching and copy-paste without choosing the commercial argument.
The salesperson checks the figures, adapts the story and owns the final proposal. That boundary reduces time without standardising the client relationship.
Select a step
How the workflow works
Select
The salesperson chooses the prospect, crop, region and programme parameters.
Assemble
The application reads three live Google Sheets and prepares the recurring parts of the deck.
Decide
The salesperson checks the figures, adjusts the argument and owns the final proposal.
03
Senior capacity returned, not just a faster document
The same recurring workload moved from around thirty hours to five each week. The difference is roughly 1,300 hours over a full year.
The annual figure converts the weekly gain. It shows scale rather than adding a separate measurement.
Bring us one workflow that takes too much time.
In 30 minutes, we will see whether it is worth mapping.
Book 30 minutes- Start with a real task
- Look at the modules involved
- Identify the control points
- Choose a clear next step