Sample project
Operations & automation
← All projectsSample project · template content
Operations & automationOne CRM in place of five pipeline spreadsheets
The weekly pipeline review comes straight from the CRM.
CRM · migration · reporting
- Client
- Add client
- Sector
- Professional services
- Year
- Add year
- Role
- Process design, setup and migration
02What changed
Before, and after.
- 01
Before: Leads in five spreadsheets
Now: One pipeline everyone works from
- 02
Before: The same contact entered three times
Now: One record, its sources linked
- 03
Before: The report rebuilt by hand every Friday
Now: A live view of the board
03How it’s wired
Where it sits in the system.
In the system·Contacts
Five lists merged into one set of contacts, duplicates removed.
In the system·Pipeline
One board, with the stages the team actually uses.
In the system·Reporting
The weekly review reads the board instead of copying it.
04The work
How it came together.
Where it started
Each salesperson kept their own spreadsheet, and the team lead merged them every Friday to see where things stood. By Monday the merge was out of date.
Image to add
What I built
I mapped how the team actually sells before choosing stages, then set up the CRM around it. The five sheets were cleaned, merged and imported, with every duplicate resolved to one record.
The Friday report became a saved view: the same numbers, always current.
05Outcome
What it changed.
- Time to prepare the weekly review
- Add a measured figure
- Duplicate contacts removed
- Add a measured figure
Client quote, if they agree to one
Built with
- CRM
- Data migration
- Saved views
06Next project
Contact
Want something like this?
Or write directly: andrewamir41@gmail.com