How It Works

Our Big Kitchen · Sydney · being tested

How it sits on the systems you already run.

This is the only page for the stack: check-in on Sevio, hosted on AWS, Salesforce and NetSuite stay the record. Home is the promise; this is the plumbing.

Layer diagram: field self-capture, Sevio experience layer, AWS hosting, Salesforce and NetSuite in parallel.
Built on what works

One platform, different lenses. Pick yours — same stack underneath.

The full stack story lives here once. Coordinators, finance, leadership, and technical leads each see the piece that matters to them.

Simple surfaces for the floor

Coordinators and volunteers use one Sevio app—not heavyweight admin consoles—for check-ins, shifts, and programme work.

  • Self-serve capture by default so you are not the bottleneck for every new volunteer.
  • Activity normalises on AWS and writes to the CRM records you already trust.
Architecture path: self-capture, Sevio on AWS, parallel CRM sync.
Module one · pilot

Built from a real kitchen day,
not a feature template. Our Big Kitchen, Sydney.

At Our Big Kitchen, check-in and credentials are live and being tested beside the person. A grant draft can start from those same records. A person still sends it.

Trust and compliance flow: credentials captured once, verified for the day, coordinator assurance view.

Why It Matters

What changes when nonprofits have the right tools.

One source of truth for programs and finance—design-intent framing, not magic metrics.

Before → After

From paper and side channels to capture at check-in.

Many teams still move meal and attendance notes through paper or ad hoc tools before they reach the CRM. Sevio is designed so frontline capture can feed the same Salesforce records you already trust—with duplicate entry as the exception, not the default.

Where it stands

Two modules. One is on the floor. One is still being built.

Module 1 is volunteer onboarding and compliance. It is live and being tested at Our Big Kitchen in Sydney. Module 2 is finding grants and drafting them. That one is in development.

On a shift, a person uploads a document. Sevio reads it, keeps personal details off the day list, and watches the expiry date. A clear result can pass. An unclear one waits for a person. An expired credential comes off the shift. A coordinator still signs off, and the step is logged.

The grant desk, while it is being built, is a list of upcoming grants, a score for how well the organisation fits, and a draft in three parts: a summary, a budget taken from real figures, and the impact story. A person sends it. Past acquittals can be kept and used again.

The record is hosted in Sydney today, and it can sit in the organisation’s own region. It is not used to train a general model. Sevio does not decide who is cleared, or who is eligible. A person does.

Personal details are taken out before they sit on the day list. The connection is encrypted. Each organisation sees only its own rows. Automatic steps are logged.

A new organisation starts with someone watching the floor. The workflow is written in plain language, then built, and someone stays for the training.

What comes next is not live: seeing a field before it is picked, and tracking food from the truck through the warehouse.

Built on AWS. DD Consulting is the technology partner.

Mission partner

Our Big Kitchen in Sydney is where Sevio is live and being tested, on a real kitchen and volunteer roster. obk.org.au →