A project's status is scattered across Google Chat, Gmail, Buganizer, and Sheets, where decisions, risks, and promises scroll past and get lost. Hellovia reads every project signal, keeps a living summary, and turns what matters into suggested work items. A person stays in charge of every decision.
A working demonstration already reads real project conversations.
Our programmes run across Google tools: vendors confirm deliveries in Chat, decisions land in Gmail threads, defects move through Buganizer, and trackers live in Sheets. A programme manager has to read all of it, remember all of it, and retype what matters between systems by hand. Things slip, not because people are careless but because the volume is inhuman.
We propose one pipeline for every project signal. The machinery is source-agnostic: Gmail, Buganizer, and Google Sheets plug into the same path from capture to review, and each new source is a connector, not a rebuild. The Google Chat connector is built first as the working demonstration.
The Google Chat connector already runs for demonstration purposes, reading real project conversations end to end: capture, living summaries with citations, suggested work items, and a review screen for each. Its AI brief is written from the real Mechanical Programme Manager job scope. Below, its unedited output from a single message.
Produced by the demonstration system during acceptance testing, not a mock-up. The summary also correctly refused to mark the delay “resolved” when a later, ambiguous “all good now” message arrived: it preserves uncertainty instead of guessing.
A programme manager stops reading every thread, holding it all in their head, and retyping what matters. The job becomes reviewing a short list of drafted items and deciding what is real, with the source one click away.
The AI suggests; it never files, assigns, or sends anything on its own. Official records only exist after a person says yes.
Each summary line and suggestion links to the exact message behind it. No floating AI opinions; you can always check the source.
The AI runs inside our own Google Cloud project. Project data never leaves the Google ecosystem and is never used to train models.
Work-item suggestions only run on conversations a person has assigned to a project. Summary coverage is a per-organization setting.
Every AI call is measured and logged, with a daily budget switch that pauses spending without losing work. At demonstration volume: well under a dollar a day.
When a message is edited or deleted at its source, Hellovia updates or removes it everywhere. Content not assigned to any project expires automatically after a retention window.
Hellovia is closed by default. Access exists only by invitation, every session is verified and revocable, and every administrative action lands in an audit trail. Walk the path a person takes:
An administrator invites each person by name into a specific role. Invitations expire on their own, can be revoked before they are accepted, and the invitation list is visible at all times.
Google sign-in or a one-time email code verifies every person, with multi-factor authentication and backup codes available on top. A new device means full verification; trusted devices are remembered per person.
Roles carry fine-grained permissions, and sessions are short-lived and bound to the organization's session policy. Any session can be revoked at any moment, one at a time or all at once.
Sign-ins, invitations, role changes, and session events are written to an audit trail with who, what, and when. Each person can see their own login activity and devices, and can end any session.