Skip to content

Workers · Taylor

Taylor, the AI account executive for your revenue team

Taylor completes the tasks a person or Parker creates: follow-up emails and drafts, scheduling and rescheduling, and the documents a task calls for, from proposals to one-pagers. It works from your customer memory and waits for your review before anything goes out.

Taylor's avatar
TaylorAccount Executive · worker
Included in every workspaceHire Taylor

Taylor is the AI account executive included with Heliyos, the AI-native OS for revenue teams. It is triggered when a task is created or updated, or when someone mentions it, and it works that task end to end: reading the brief, the account memory and the thread, drafting the follow-up email or proposal, proposing meeting times, and producing documents as artifacts on the task. Taylor updates the task stage and reports what it did, what it found and what Parker should change on the account. Outbound email waits for approval by default.

The job

What starts it, what it may use, what waits for you

Starts when

  • A task is created or updated
  • Someone mentions @Taylor in chat or on a record

Can use

  • Send email and create drafts through your inbox
  • Schedule, reschedule and cancel meetings
  • Web search for context
  • Write notes and documents: proposals, one-pagers, decks, spreadsheets

Needs review

  • Outbound email, until you change the rule
  • Calendar invites to customers, if you choose
  • Documents shared outside the workspace

Use cases

Use cases

  • After the call, the recap writes itself

    Parker creates the task from the transcript; Taylor drafts the recap with the decisions, the open questions and the next step, in your voice, waiting in Reviews.

  • "Send us the proposal by Friday"

    Taylor builds the proposal from your pricing sheet in Drive and the account memory, attaches it as a PDF artifact and drafts the cover email.

  • "Can we do next Tuesday instead?"

    Taylor proposes times from your calendar, holds the slot and sends the invite after you approve.

  • A reply asks a question your docs do not answer

    Taylor searches the web, cites what it used, and flags the open question on the task instead of guessing.

  • Twelve follow-ups due today

    Each one is a task. Taylor works them in order, and your Reviews queue has twelve drafts with evidence by 9am.

A day with the worker

Every step shows its evidence

Sun marks the step running right now. Finished steps go quiet. Anything important waits for a person.

  1. 09:12
    Task created by Parker: "Send the proposal to Namora after Tuesday’s call"From meeting · QBR with Namora · 5 attendees
    Done
  2. 09:13
    Read the brief, the transcript and the account memoryPricing discussed: Business tier, 40 seats · objection: SSO timeline
    Done
  3. 09:15
    Wrote the proposal as a PDF artifactproposal-namora.pdf · 6 pages · from the pricing sheet in Knowledge
    Done
  4. 09:16
    Drafting the cover emailReply on thread "Re: QBR follow-up" · recipients: Sarah Kim, Daniel Ortiz
    Running
  5. 09:17
    Email and proposal wait for approvalRule: outbound email needs review
    Needs review

Trust grows in steps

Hand off more over time

  1. 01

    Everything reviewed

    Every email, invite and document waits in Reviews. You see how Taylor works before it acts alone.

  2. 02

    Routine goes through

    Recaps and reschedules you always approve unchanged move off review. Proposals still wait.

  3. 03

    Taylor runs the follow-up

    For accounts you choose, follow-up email sends without a stop. Evidence stays on every message.

Review ladder

Start with everything reviewed

  1. 01

    Review everything

    The default. Every outbound action waits for a person. Best for the first weeks.

  2. 02

    Review what matters

    Routine recaps send. Proposals, pricing and new contacts still wait.

  3. 03

    Trusted on named accounts

    On accounts you pick, Taylor sends follow-ups on its own. Evidence stays on every message.

Workers work together

A team, with handoffs.

Workers are not isolated bots. They hand work to each other, stop and hand it to a person when it matters, and share one memory and one knowledge base, so the work moves without anyone re-explaining the account.

Parker's avatar Parkerread the QBR transcript and created the taskTaylor's avatar Taylorwrote the proposal and the cover emailNeeds review · Sohamapproves, and it sends

  • Workers hand work to each other

    Parker reads a meeting and creates the follow-up task; Taylor picks it up, does the work and reports back what Parker should change on the account. The handoff is visible in the thread: "Parker handed off to Taylor".

  • Workers hand work to a person

    When an action matches a review rule, or a worker is unsure, it stops and hands the decision to the account owner in Reviews, with the evidence and its open questions. A person approves, edits or answers, and the run continues.

  • They share one memory and one knowledge base

    Every worker reads the same account memory and the same organisation knowledge: your pricing, docs, custom fields and files. What one worker learns on an account, the next one knows.

  • You can talk to them, and they talk to each other

    Mention @Taylor or @Parker in chat or on a task and they reply with what they did and why. On a task, workers talk among themselves to split the steps, and the conversation stays on the task for you to read.

FAQ

Questions people ask

What does an AI account executive do?
In Heliyos, Taylor completes sales tasks: it drafts and sends follow-up emails, schedules meetings, writes proposals and other documents, and reports the result on the task, with a person reviewing anything important.
Will Taylor email my customers without asking?
Not by default. Outbound email waits in Reviews until you change the rule, and you can keep it that way for as long as you like.
How does Taylor know my pricing and product?
From the knowledge base you upload (decks, pricing, docs) and from the customer memory on the account. It cites what it used.
Can Taylor create tasks for itself?
No. Tasks come from Parker, from Scouts or from people. Taylor works them and reports back.
Can I give Taylor a different name or scope?
Taylor’s job is fixed so the team knows what to expect. For a different scope, deploy a custom worker with its own role description.

Taylor is ready. Deploy it today.

Closed beta, usage-based pricing, no seats. Join the waitlist and we review your request.

Closed beta. We review every request and reply by email.