Requests move through chat and email.
No one knows what is waiting, who owns the decision or which document is missing.
We design the operational layer around accounting: budget control, expense workflows, fund utilisation, project delivery, task ownership, documents and approvals. Finance keeps the books; connected operations give every team the right view before month-end.
Accounting software can be accurate while project owners still cannot see budget pressure, approval status or what evidence finance needs from them.
No one knows what is waiting, who owns the decision or which document is missing.
Project and grant owners manage commitments in parallel sheets because actuals are hard to interpret.
Owners, dependencies, risks, documents and time live across disconnected tools.
An operations system earns its place when a requester, a budget owner and the finance team each open it and see what is waiting, on whom, and against which budget.
One request, one history. Evidence, approvals and the accounting hand-off on the same record.
Budget pressure before month-end. Approvals, missing evidence and spend signals in one queue.
Actuals and commitments together. Programme owners see the same figure finance reports.
Illustrative screens with sample data. Not a live partner record.
The operational system should preserve accounting boundaries while giving teams timely, role-appropriate information.
We design requests, approvals, allocations and management views around the accounting source of truth and the organisation’s control process.
Programme, project, grant, cost centre and budget-head structures with approved changes and version history.
Purchase, travel, advance, expense and payment workflows with thresholds, evidence and accountable decisions.
Map commitments and actuals to the correct programme, grant or project and surface variance early.
Validated records, reconciliation status and integration boundaries for tools such as Zoho Books or Tally.
The accounting ledger and statutory treatment remain with the organisation’s authorised finance process. We design the operational records and controls that feed it reliably.
Project systems are useful when they reflect how decisions, documents, risks, time and money move—not when they become a second to-do list.
Projects, milestones, workstreams, owners, dates, dependencies and shared definitions of done.
Tasks, recurring routines, approvals, risks, decisions and escalation with a clear operating cadence.
Timesheets where useful, document control, planned effort, commitments and the finance handoff.
Progress, blocked work, capacity, risk and budget signals that trace back to owned actions.
Campaigns, journeys and events can sit inside this operating layer when they need to feed a donor, participant, member or partner record. We design segmentation, consent, ownership and response handoffs before choosing campaign tooling.
Segments, interests, communication preferences and lawful, organisation-approved consent handling.
Messages, events, automations, responses and conversion into a real relationship or programme workflow.
Every operations system follows the same ImpactOS stages and sign-off points, so you always know what is being decided, by whom, and what you will have at the end of it.
We follow one request from need to payment with the people who raise, approve and book it.
Budget structure, thresholds and roles first, then the boundary with the accounting system.
One approval flow first, tested with real requesters, approvers and finance.
We track whether requests and approvals move through the system, not just logins.
A retrospective on what worked and what the next release should be.
Operations is often sequenced after programme, funding or HR records are stable. See the five-stage transformation pathway →
The pattern transfers; the exact budgets, approvals and integrations change with each organisation. Full case studies live on edzola.com.
Skilling · connected operations10+Future Perfect runs admissions, payments and refunds, the learning platform, Zoom and WhatsApp through one system, with screens for trainers, telecallers and verifiers.
Read the case study ↗ Project delivery · Zoho ProjectsProject delivery and team collaboration brought into one shared, accountable system.
Read the case study ↗ Money in, money outDonations, receipts, approvals, grant tagging and fund reports. On Zoho Books, as a Zoho Creator app or as a custom application. A person approves before anything reaches the books.
Explore FundZola →Our own products plug into an operations system once budgets, approvals and the accounting boundary are clear. People keep every decision about money.
AI suggests the grant and programme head for each expense from your allocation matrix; you confirm before it reaches your books. Utilisation reports follow.
Explore FundZola → DozAI · RunDocument completeness is one of the missions we are shaping: chase every missing bill or approval note and hand unclear cases to finance.
Explore DozAI → ZolaShield · ProtectSee where personal data in finance records, sheets and inboxes carries risk, with a prioritised 180-day plan to fix it.
Explore ZolaShield →If yours isn’t here, bring it to the first call. We’d rather answer it honestly than have it surface halfway through a build.
No. The accounting system stays the source of truth for the books. We design the requests, approvals and allocations that feed it, and the hand-off between them.
Yes. Thresholds, roles and routes are configured, not hard-coded, so the workflow can follow policy changes.
Yes, with commitments alongside actuals so pressure shows before month-end. Finance decides which figures are final.
No. We profile what you have, agree a cut-off date and migrate only what earns its place, keeping the source files and a transformation log.
Cost follows records, roles, integrations, migration and support. We show expected running costs, including licences, up front. Eligible nonprofits can access subsidised delivery through the Built for Impact Programme.
No. FundZola suggests tags and matches; a person approves before anything is written to Zoho Books.
Use these resources to clarify the operating model before configuring tools.
See where fundraising, grants, programmes and accounting must meet.
Open chapter 2 →Interactive field guideModel the work, align the team and only then power it with automation.
Open chapter 5 →Digital transformationMove from current-state understanding to sustainable digital change.
Read on edzola.com ↗Data architectureUse centralisation deliberately without forcing every job into one tool.
Read on edzola.com ↗Marketing operationsAn introduction to audience journeys and repeatable campaign workflows.
Read on edzola.com ↗Shared infrastructureWhy reusable patterns and supported tools can compound value across organisations.
Read the essay →Budgets and projects become more useful when they link to grants, people and programme evidence.
Bring one budget, approval flow, project tracker or expense process. We will identify where ownership, data and decisions drift apart and what to connect first.