Case Study · Zoho Implementation
Connecting Sales, Finance, and Procurement Across Two Sites
Our client runs a business with sales handled from a single site and operations spread across two sites, each keeping its own accounts. We connected the sales pipeline, site-level finance, and procurement process into one Zoho environment, with each part structured around how the business actually operates.
One sales pipeline. Two sites. One connected system.
01 · The business
One sales effort, two sites, and a procurement process in between.
The sales team works a single pipeline, moving opportunities from first contact through to a closed deal. The business then operates across two sites, each with its own accounts and financial records.
Between sales and site-level finance sits procurement: requests for materials or supplies need to be raised, approved, ordered from a vendor, and ultimately reflected in the correct site's books.
As the business grew, keeping the pipeline visible, the two sites' books consistent, and procurement requests from getting lost in email became harder to manage.
The business needed its existing Zoho tools to work as one connected environment, not as separate systems.
02 · The challenge
Three connected processes, with nothing actually connecting them.
Sales, site finance, and procurement each needed their own structure, but none of them were connected. That meant visibility and accountability suffered at the points where information moved from one process to another.
Sales pipeline
Track opportunities through a consistent pipeline the whole team can see.
Two-site finance
Keep each site's accounts separate while maintaining a consistent structure for comparison.
Procurement requests
Raise, approve, and track requests instead of managing them through email.
Purchase to books
Connect an approved request to a purchase order and the correct site's financial records.
Management visibility
Give ownership a clear view across sales, finance, and procurement without manually pulling information from different places.
One connected environment
Make the Zoho tools work together rather than operating as separate applications.
03 · The approach
We built around three real processes, not one generic template.
Sales, two-site finance, and procurement each have different requirements. Rather than forcing them into one setup, we used the Zoho tool best suited to each process and connected them into one environment.
The goal was for the sales pipeline, procurement requests, and site-level accounts to reflect the same underlying business activity without unnecessary manual re-entry.
The right Zoho tool for each process.
- Bigin
- for the sales pipeline.
- Books
- for each site's accounts.
- Creator
- for the custom procurement workflow.
- Connected
- so information can move between them.
04 · How it works
Sales, procurement, and site-level finance, connected.
An opportunity, a procurement request, and the resulting cost now move through one connected environment instead of being managed as separate processes.
Zoho Bigin — Connected Pipeline
One sales pipeline with consistent stages, deal values, and follow-ups visible to the team.
Zoho Books — Two-Site Accounting
Each site keeps its own books, matching how the business is structured, with a consistent setup for review side by side.
Custom Procurement App
Purchase requests, approvals, and vendor tracking built around the business's own approval chain.
Connected Across Sites and Apps
Procurement requests link to the correct site, so an approved purchase carries that relationship through to the financial records.
05 · What changed
Three processes that now genuinely connect.
The result is not simply three Zoho applications configured separately. The implementation connects sales, finance, and procurement around the way the business is actually structured.
One pipeline the whole team can see.
Sales opportunities are tracked consistently in Bigin instead of living across memory and personal spreadsheets.
Two sites' books that still add up.
Each site's accounts remain independent in Books, while the consistent structure makes comparing or combining them straightforward.
Procurement that's finally visible.
Requests, approvals, and purchase orders are tracked in one custom app instead of moving through email with no clear status.
Costs land in the right place.
A procurement request tied to a site carries that relationship through to the purchase order and resulting books entry.
One environment, not three separate systems.
Bigin, Books, and the custom Creator app sit inside the same Zoho environment and are connected around the business process.
06 · Built around the client
Built around how the business is actually structured.
Two sites stayed two sites in the books. The sales pipeline stayed unified. Procurement was designed as its own process and connected to the right site.
The implementation was shaped around the structure that already worked for the business, rather than forcing everything into a single-site or single-ledger template.
One sales pipeline. Two sites. One procurement process.
The technology reflects the way the business operates, so the system supports the existing structure instead of asking the business to restructure around the software.
“The technology fits how the business is structured, rather than asking the business to restructure around the technology.”
Let's pave the way
Running sales, finance, or procurement as separate efforts that don't talk to each other?
Every growing business eventually needs its pipeline, its books, and its procurement process to connect — especially once more than one site is involved. Let's look at what a connected Zoho setup could do for yours.