Commercial direction
An operator-led sector deployment with scoped implementation, support and a proposed service-network licence. The EBFC environment informs the pilot; repeatability must be shown before wider rollout.
CommunityOS / local people. Connected care.
A meal opens
the door.
Keep the
connection.
From community meals to community care. Give the people delivering support a system that follows through.
EBFC pilot development
The ambition isn’t to automate kindness.
It is to support the people delivering it.
Meals. People. Follow-through.The service beyond the kitchen.
EBFC pilot developmentOriginal product concept · investor showcase
Refer→Prepare→Deliver→Check in→Stay connected.
Inside CommunityOS
The whole service.
In working view.
Explore the kitchen, route and welfare handover. These are interactive sample records, not live recipient data.
CommunityOSEast Brighton / sample serviceILLUSTRATIVE WORKSPACE
Illustrative map · no live tracking
NEXT SAMPLE STOP / DEMO-012
A delivery.
And a check-in.
The meal and the visit belong together. Capture the outcome. Keep any concern connected to a responsible person.
Meal readyDietary notes attached.Ready
Visit contextSample route and delivery notes.Linked
Demo only. No real visit or case is updated.
Driver handovers Keep the route, recipient context and doorstep outcome together.
Concept illustrationKITCHEN / SAMPLE BATCH
Good food.
Organised before the door.
Vegetable currySample batch A · dietary notes linked.12 meals
Soup & breadSample batch B · packing checklist.8 meals
Individual needsReview special preparation notes.4 meals
No live kitchen record is changed.
Kitchen planning Connect dietary information, preparation and packing checks to the dispatch handover.
REFERRAL INTAKE
Start with the person.
Keep the request organised.
DEMO-010Initial request to review.New
DEMO-011Support context to check.Review
DEMO-012Delivery follow-through.Linked
Designed for a human service
Referral context, dietary requirements and agreed support belong with the case. Access and operational responsibilities are defined for the deployment.
Accessible service intake Bring referrals, assisted requests and recipient preferences into the service plan.
The visit doesn’t
end at the doorstep.
Keep a concern linked to the visit and route it to the appropriate person. CommunityOS supports the handover; it does not replace professional judgement or emergency services.
SAMPLE FOLLOW-UP QUEUE
DEMO-012
No new sample concern. Use the Dispatch tab to explore a doorstep handover.
Awaiting demonstrationWelfare follow-through A concern gets a responsible human next step, with the relevant visit context attached.
VOLUNTEERS / SAMPLE ROSTER
People make the service.
Volunteer AKitchen preparation.Ready
Volunteer BSample delivery route.Assigned
Volunteer CCollection support.Available
The right support for the right role
Connect shifts, availability, routes and responsibilities. Make the working day easier to understand—for the team in the kitchen and the person out on the road.
Volunteer coordination Match availability and responsibilities to the day’s service. Every volunteer can see their next task.
ILLUSTRATIVE ACTIVITY / NOT IMPACT EVIDENCE
Show what happened.
Then evaluate what changed.
A useful evidence trail
- Meals and visits recorded
- Follow-ups and handovers visible
- Pilot outcomes agreed before evaluation
- No invented health or cost savings
Service evidence Trace the service from referral to meal, delivery and follow-up. Give partners a record they can review.
Concept sceneThe East Brighton starting point
Built around
the work that
already matters.
CommunityOS is being shaped around East Brighton Food Co-op’s service loop. Not technology looking for a cause. A real operating challenge giving the technology a purpose.
Referrals. Food. Volunteers. A visit. A concern that needs following up. Connect the practical detail so local care has room to grow.
Meals first.
Human contact.
Better support.The ElevnAI design intention—not a measured outcome claim.
The investment conversation
A meal opens the door. The connection must not end there.
CommunityOS is being shaped around East Brighton Food Co-op’s service loop. The opportunity: support the whole journey, not just one task. Give the people delivering care more time, better context and a clearer next step.
The next proof point
Trace a complete referral-to-doorstep journey. Measure coordination effort against a baseline. Show responsible human escalation and a repeatable operator setup.
EBFC pilot development