Winston

Voca AI - The AI project manager that runs in the background

by
Voca is an AI PM that connects to Slack, GitHub, and Linear and keeps project status in sync with reality. It builds a real-time project knowledge base you can query, and you can set up skills and automations so it runs in the background 24/7 without chasing status updates.

Add a comment

Replies

Best
Artifactly

Love where you're going with this. Could be over the head of the current gen of project teams but I could see this getting legs with the next gen of project teams.

Winston

@artifactly Thanks, appreciate that. I think the “next gen” is really a lot of today’s teams once they start using AI agents to cut down the manual coordination work and improve efficiency. That’s what we’re trying to enable with Voca.

Andrew Chernyshev

Hey guys! It seems cool to get continuously synced on the progress.
But can you help me imagine what’s the exact moment or event in Voca AI that makes me think: "This is worth paying for"?

Winston

@andrey_chernyshev1 Great question. The “worth paying for it” moment is when you realize you stopped chasing people for updates, but you still know what’s moving, what’s blocked, and what’s starting to slip. You check the morning brief and it’s already pulled together from Slack, GitHub, and Linear, with links back to the original messages and PRs so you can trust it. For small teams with no PM, it cuts down the daily “any update?” messages. For teams that do have a PM, it takes a bunch of the repetitive coordination work off their plate.

Andrew Chernyshev

@winstonqian Yeah I feel it too, it's a good promise, but I cant imagine an a specific event, this aha moment is all about something doesn't happen.
I mean it's hard to rely and track (or even notice) something that doesn't literally happen.

It came curious for me so I decided to ask my product management co-pilot about this.
It brought me a funny idea: create a button "cancel status meeting" right under the report, and track the % of meeting canceled

For more details, that's what is said:

Segmentation for Voca (how we think about the market):

Segmentation parameters

  • Team size & process maturity – small vs mid/large teams face different levels of coordination overhead and ceremony.

  • Work mode – office vs distributed teams; the more async the work, the harder it is to see the real state of a project in one place.

4 segments (in 2x2 matrix)

  1. Small office teams – rely heavily on conversations and quick syncs; tracker drift is annoying, but easy to fix with a meeting.

  2. Small distributed teams – work lives in Slack + GitHub + tracker; statuses fall out of sync fast and only a few people see the “real” picture.

  3. Mid/large office teams – more process and reporting, partial visibility is solved through meetings and formal rituals.

  4. Mid/large distributed teams – many projects and tools, heavy processes, often their own internal automation.

Focus recommendation

It's better to focus first on small distributed product teams (≈5–20 people), because they:

  • feel the “tracker ≠ reality” pain the strongest,

  • have low process/bureaucratic inertia,

  • can quickly adopt an AI PM that plugs into their existing Slack + GitHub + tracker stack.

  • Context – Small remote / hybrid product teams (5–20 people) working in Slack + GitHub + a tracker (Linear / Jira / Notion). No heavy PMO, founders and leads are still deep in day-to-day operations.

  • Core problem – The tracker quickly drifts away from reality, while real project status is hidden across Slack threads, PRs and issues. Only 1–2 people truly know what’s going on.

  • How they search for solutions – They don’t want a new system of record, they want something that sits on top of their existing stack. Anything that needs heavy setup, new rituals or training is an instant “no”.

  • How they decide to pay – The buyer is usually a founder / CPO / CTO / lead PM who wants fewer blind spots and fewer nasty surprises. Their main fear: “yet another tool no one updates” and “can I trust AI without double-checking everything?”.

  • How they want to use it – They expect an assistant, not another dashboard: insights should come directly into communication. Value is measured by fewer status meetings, earlier risk signals and less time spent manually reconstructing what’s really happening in the project.


Aha metric: % of active teams that skip at least one status meeting because of Voca (e.g. click “Skip status meeting” in the Slack summary) within their first 14 days.

Winston

@andrey_chernyshev1 Thanks for the suggestion. The “Cancel status meeting” button right under the report is a great idea.

To make the value obvious, we’re adding an impact metric and leading with “hours saved” since it’s easy to understand and accounts for meeting length. “Meetings canceled” can show up as a supporting metric too, like “X meetings canceled (Y%).”

We will ship this in our next update.

Akmal Arzhang

Why'd you provide step by step instructions to a PM?

Winston

@akmal_arzhang Haha, yeah. We weren’t trying to give PMs a checklist. The goal is the opposite: give PMs leverage by keeping project context up to date automatically so they spend less time on follow-ups and more time on planning and decisions.