Case study · Fairglow
A company knowledge base that gave the team eight hours back.
After a €3M seed round, Fairglow needed sales, product and customer teams to work from the same account context without rebuilding it after every call.
The same context was rebuilt several times
Useful information existed in calls and conversations, but it was not connected in one company record. A resolved objection or product decision could be searched for and rewritten again in the next proposal.
The need crossed several teams. The base had to serve sales without becoming another documentation tool to maintain separately.
Useful knowledge was spread across the company and proposal work repeatedly started from fragments rather than one dependable base.
Before
Knowledge had to be found and assembled again for each proposal.
What Basalt built
Basalt created a company knowledge base and a proposal workflow that prepared the recurring work for human review.
After
The team recovered eight hours each week and moved from scoping to production-ready agents in ten days.
Key figures
8 h
recovered each week
Recurring time returned each week.
+25%
sales velocity
Observed change in the pace of the sales process.
10 days
from scoping to production-ready agents
From scope to production-ready agents.
02
Shared memory before generation
Basalt first connected calls, needs, objections, requests and decisions to the right company. The proposal workflow then uses that context to prepare recurring work for the responsible person.
The team still reviews the proposal. The system prepares a coherent starting point; it does not decide the offer or what should be promised.
Select a step
How the workflow works
Capture
Attach a sales or customer call to the right company and retain the facts that matter.
Connect
Build one account record from needs, objections, requests and previous decisions.
Prepare
Prepare the relevant proposal or weekly synthesis for the responsible team to review.
03
What the three figures say together
Ten days covers the move from scope to production-ready agents. Eight hours measures weekly time returned once the workflow was in use.
Sales velocity adds a signal about pace. It does not replace the time measure or imply that every commercial change came from the system alone.
“We went from scoping to production-ready agents in ten days. I’ve tried building this myself, it’s way harder than it looks.”
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