Case study · Engineering, procurement and construction (EPC)
PPS Consulting India designed and built the operating model for a young solar and storage contractor in Africa, from discovery to handover. 100+ artifacts in all: an operating manual, a governance framework, 8 master standard operating procedures (SOPs), 13 policies, 24 SOPs, 45+ trackers, role playbooks, and hiring packs for the people who would run the projects.
100+ artifacts
8 master SOPs, 13 policies, 24 SOPs, 45+ trackers, role playbooks and hiring packs
The founder was building an engineering, procurement and construction business and needed its operating model written down: who decides what, how a project moves from contract to handover, how money is approved and paid, and what each new hire is accountable for.
The people who would run the projects were still to be hired, so the model also had to tell each of them what they would be accountable for.
Interviews with the founder and the operations team, a map of the as-is operating model and its strain points, and an operating framework blueprint signed off before anything was built.
The operating manual and a governance framework: tiered decision rights, delegation thresholds, approval flows, the meeting cadence, and document control and version policy, with a performance management framework alongside.
SOPs, policies, role playbooks, trackers and guides for three areas: project delivery and engineering, supply chain, and corporate support. Tools designed to be independent of any software: spreadsheets first, portable to any platform later. Hiring packs for the execution roles: terms of reference for the Project Director, Assistant Project Director, Site Manager and Coordinator, a contract template with incentive and field-deployment annexes, and playbooks for each role's execution duties.
Retained at half capacity with two working sessions a week: new hires coached in, SOPs refitted to how the work really happened on site, and financial controls checked in practice.
Final versions archived, hand-off routines defined, an internal SOP steward named, and a maturity roadmap for what to build next.
Project delivery and engineering
2 master SOPs · 2 policies · 9 SOPs
Process SOPs
Role playbooks
Templates and trackers
Supply chain
1 master SOP · 2 policies · 7 SOPs
Process SOPs
Role playbooks
Templates and trackers
Corporate support
5 master SOPs · 9 policies · 8 SOPs
Process SOPs
Role playbooks
Templates and trackers
Tools, designed to be software-independent
Hiring packs for the execution roles
Governance in practice
The engagement
Retained advisory on capacity, not a fixed-deliverable contract. Priorities rebalanced with the founder as the business changed; decisions written down in plain language; work shared across three time zones.
An internal SOP steward owns the library. Final versions are archived, hand-off routines are defined, and a maturity roadmap sets out what to build next.
It is if:
With the PPS Backbone Review: four weeks, a fixed fee of ₹1,50,000 to ₹3,50,000 plus GST and expenses, one fix working by the end, and a plan with owners and measures that is yours to keep, whether or not we build it with you.
How the Review works642 hours
leading the office through a finance and accounting transformation with a budget above US$5 million
Relevant if you have an internal team that takes requests from across the business and can't say yes to all of them.
One org chart
for every employee, contractor and outsourced team, with costs, budget against actual, and scenarios
Relevant if your people costs are spread across payroll, contractors and vendors, and nobody can show the total.
90 days
from naming owners to the company's own team running the weekly cadence
Relevant if you are taking over a family business and the way it runs still lives with the founding generation.
Running now
Our newest articles on the problem this case shows.
The Cognitive Load Trap · part 1 of 4
The decisions, exceptions and rules a founder carries in memory make an inbox nobody else can see. How it stalls a business, and how to start emptying it.
Let Go to Grow · part 1
Teams trust a system only when their leader follows it first, most of all under stress. What the Trust Loop is, and five steps to build it.
Across Upwork and direct contracts, including the people on our project teams.
The written answer to how the company runs: who decides what and up to what amount, how work moves from one role to the next, which policies apply, and which tracker or form each step uses. Here that was an operating manual and governance framework, with SOPs, policies, role playbooks and trackers underneath, and hiring packs for the people who would run it.
So the process is proven before it is locked into software. Every tracker was designed to run in a spreadsheet first and to move to any platform later, which keeps the operating model independent of one vendor.
This one was, across three time zones: two working sessions a week, decisions written down in plain language, and priorities rebalanced with the founder as the business changed.
What you're trying to achieve in the next 90 days, and what's breaking in execution. We'll tell you plainly what we'd fix first.
Book a discovery callFree, no obligation, and under an NDA if you prefer.
Or write to consult@ppsconsulting.biz WhatsApp +91 93246 21840 (opens in a new tab)
