// FOR OWNER-LED BUSINESSES THAT RUN ON WHATSAPP AND SHEETS
Your operation runs on WhatsApp, spreadsheets, and people who hold it all together.
We've seen this. We build the system that lets your team focus on the work — not the workarounds.
// DIAGNOSTIC_PHASE_02
If any of this looks familiar —
the system was never designed for what you've grown into.
These are operational symptoms. Each one has a structural cause — and a structured fix.
Customers wait for answers your data already contains.
There is no live count. Decisions are made by eye, and the first sign of a stockout is a customer complaint.
Your staff carry critical process knowledge — in their heads.
Onboarding is slow, errors are personal, and losing one employee means losing institutional memory.
Orders arrive through WhatsApp, calls, and walk-ins — all at once.
There is no single source of truth. Fulfilment errors are a recurring tax on your margin.
Your reporting is a month-end spreadsheet.
By the time the data is assembled, the window to act has closed. You are managing history, not the present.
Approvals happen on the phone between the owner and the manager.
Nothing is recorded. Accountability is informal and exceptions become the norm.
You have three systems that don't speak to each other.
Accounting, operations, and communication are siloed. Reconciliation is a manual, weekly ritual.
Growth makes things harder, not easier.
A second location doubles your headaches. The operation does not scale because the process was never formalised.
You built a workaround — and now the workaround has workarounds.
Each patch adds fragility. The system is held together by individual heroics rather than reliable structure.
Recognise any of these?
Most of what you've just read has a structural fix. Start by mapping the one that's costing you most.
// HOW_WE_OPERATE
The work has a sequence.
Observe. Map. Name.
We spend time inside your operation before writing a single line of code. The first deliverable is always a plain-language map of how work actually flows — not how you think it flows.
Design the system around the constraint.
Most operations have one or two points of real friction. We identify the constraint, design a minimal structural fix, and validate it with your team before building anything permanent.
Build, train, hand over.
The technology we implement is only as good as the adoption it achieves. Every system we deploy includes a structured handover and a training protocol your staff can actually follow.
Three steps. No surprises. No SaaS sprawl. — Technology bends to the business.
// OPERATIONAL_VIGNETTES
The signs of a system stretched thin.
The Stock Inquiry Loop
Repeated customer queries about stock availability that the data could answer — but a human has to.
// DIAGNOSIS: Customer queries route to humans who manually look up sheets. Slow responses. Lost orders. After-hours blind spot.
// IMPACT: Customers get accurate answers in seconds. 24/7 availability. Sales team freed to sell, not search.
The WhatsApp Logjam
Orders, approvals, and follow-ups stacked across threads. The owner becomes the bottleneck.
// DIAGNOSIS: Ad-hoc communication means lost context, duplicated effort, missed approvals, and owner-as-router.
// IMPACT: Structured intake captures every request. Routing is automatic. Owner attention freed for owner-only decisions.
The Spreadsheet Spiderweb
Month-end reporting takes days. One person knows the formulas. Critical errors compound silently.
// DIAGNOSIS: Reactive reporting from manual spreadsheets. Single-owner data dependencies. No live view of operational reality.
// IMPACT: Reports run from clean live data. Errors caught at source. Today's numbers visible today.
The Shift Handover Gap
Operational state lost between shifts. Reorders missed, prep miscounted, customer issues fall through.
// DIAGNOSIS: No structured handover protocol. Knowledge transfer happens verbally or not at all.
// IMPACT: Shift state captured digitally. Critical items surfaced to the next shift. Continuity preserved across opening hours.
The Subscription Bloat
Software licences paid for in full. Used in fragments.
// DIAGNOSIS: Workspaces with seats for people who only need one shared sheet. Premium subscriptions running for features nobody uses. Auto-renewals invisible until the next billing cycle.
// IMPACT: We audit what you're paying for versus what's actually used. Right-size what stays. Eliminate what doesn't. Recurring savings often fund the next engagement.
Does one of these look like your operation?
We've worked inside businesses shaped like yours. The first conversation is diagnostic — no proposal pressure.
// OUR_PHILOSOPHY
Small. Sharp. Effective.
Porcupyn is a principals-led practice. Based in Sri Lanka. Working across the region with owner-led businesses that have outgrown the workaround.
We don't deploy SaaS. We don't sell licences. We work inside your operation, find what's broken, and build the fix using tools your business can sustain.
The systems we build are designed for the people on the floor — not the boardroom. If your staff won't use it, it's not a solution.
// THE UNASKED QUESTIONS
Before you ask — here's what to expect.
Weeks, not months. Each intervention is scoped to deploy fast.
Atomic. One problem solved properly. Then the next.
The system. Not a licence. Tooling fits your operation, not a vendor's roadmap.
First fix demonstrates value. Then we talk about the layer above it.
// THE_MANIFESTO
Rules of Operation.
Work flows where it's easy, not where it's told.
If the floor won't use it, it's not a solution.
Complexity is a tax on execution.
Design the system around the constraint.
Manual work isn't the enemy; blind work is.
Tooling fits your operation. Not a vendor's roadmap.
Technology bends to the business.
// INITIATE_DIAGNOSTIC
Ready to find
the constraint?
Stop guessing where the friction is. Start by mapping the reality of your operation.