Insights
What we find
inside real businesses.
No theory. Everything on this page came out of work we have actually done. If it is here, we have fixed it for someone.
Work we have done
Real numbers from real jobs.
19,133
call records we checked one by one
We read every row in a calling sheet and compared it to what actually happened on the call.
14,611
records moved into one CRM
Everyone with a phone number and a real call history, in one place instead of spread across lists.
3,709
call recordings saved
A supplier was about to switch the links off. We copied every recording before that happened.
856
deals moved, none lost
Two separate boards joined into one. Nothing went missing, and we kept a list of every change.
8,682
deals now on one board
Pulled together from three different lists. We counted them all. Nothing was left behind.
50 / 0
automatic runs, zero failures
The last fifty times the system ran on its own, it worked every time.
These are jobs we have done, not results we are claiming. We do not publish client names or anyone's revenue.
What it looks like
The problem is rarely missing data.
It is quietly wrong data.
Three things we opened up and counted. Each one looked fine from the outside until somebody read every row.
0 / 10,850
9.5%
Call notes that did not match the outcome
We read every row. On these, the note said one thing and the result said another. Nobody had spotted it, because nothing made anyone check.
0 / 1,568
45%
Records already sitting on the main board
One business ran two pipelines and believed they had two sources of leads. Nearly half of the smaller one was the bigger one, twice.
0 / 324
81%
Messages confirmed delivered at the carrier
The other 60 were carrier-blocked and scrubbed from the list. Without checking at carrier level, this reads as a dead list. The list was fine.
Counts of work performed on delivered engagements. AS Ventures does not publish client names, conversion rates or return figures.
Articles
Longer reads.
How to tell if your CRM is losing you deals
Twelve things you can check yourself in about an hour. Most people find at least four of them broken.
3 September 2026 · 8 min read
ReadWhy growing businesses outgrow spreadsheets
Seven signs the sheet has stopped helping and started costing you. What to fix before you buy another tool.
10 September 2026 · 7 min read
ReadCRM adoption is an operating change
Why teams quietly abandon a new CRM, and the eight steps that make it stick.
10 September 2026 · 8 min read
ReadBuy software without buying complexity
Seven rules for choosing a tool that actually gets used. Start by never buying from a demo.
10 September 2026 · 7 min read
ReadTurn hidden work into a repeatable system
Map what your team really does, then write it down so a new person can follow it alone.
10 September 2026 · 8 min read
ReadBuild reports people can act on
Fewer numbers, every one traceable, exceptions first, and nothing that fails silently.
10 September 2026 · 8 min read
ReadDesign the calling handoff properly
Which calls to automate, the controls to set before the first dial, and how to hand over to a person.
10 September 2026 · 8 min read
ReadWhat we keep seeing
The same problems, in almost every business.
Your data
Your call notes and your call results often do not match
We looked at 10,850 calls. On 1,032 of them, the note said one thing and the result said another. Nobody had spotted it, because nothing makes you check.
Your CRM
A second pipeline is usually the same people twice
One business ran two boards. Of the 1,568 people on the smaller one, 712 were already on the big one. They thought they had two different sources of leads.
Your CRM
Never wire anything to a stage's ID number
Do that, and the day someone adds a new stage, part of your system quietly stops working. Use the stage name instead and you can add stages whenever you like.
Your setup
Old unused code is what breaks things
One file had the same job written out twice, eighteen times over, plus about 1,060 lines that did nothing but looked like they did. Nobody could tell which version was actually running.
Your reports
If a job stops running, you should be able to tell why
Build it so a finished job switches itself off and writes down when. Otherwise silence looks like a breakdown, and people stop trusting the numbers.
Your reports
Open the finished report and actually read it
Three problems in an automatic report got past every technical check. We only found them by reading the report the way a customer would.
Your setup
Never let a script change your live data on the first run
Every one of ours does a practice run first and shows you exactly what it would change. That is how 601 records got fixed in one go, with nothing to undo afterwards.
Your costs
Free public data replaced something a client was paying for
Flood, land height, soil and water information all come from free government sources now. If a figure is not available, the report leaves it blank instead of guessing.
Next step
Want us to just look at it?
Show us what you have got. We will tell you what is wrong with it and what it would take to fix.