Eduard

@Eduard, the AI coworker who works the way your team does

Mention @Eduard like any coworker. He knows the context of your company or project, acts on his own, suggests what to take on next, and learns from your whole team.

Hire Eduard for your team Get started in 2 minutes

Works with the tools you use

Slack Linear GitHub
Slack window with Eduard working with a teammate in a channel

AI assistants work for one person. Eduard works with your team.

Eduard Personal AI assistants
Where you talk to it Slack, GitHub and Linear, like any coworker Its own app or chat window
Who works with it The whole team, in the same thread One person, who copies results back to the team
Who starts the work You, or Eduard: he suggests what to pick up You, every time
What it follows through on Initiatives for the team, for weeks Tasks you set up for yourself
What it learns What one person teaches him, everyone gets Stays with one person

Gets work done across departments

Ask him for something, put work on a schedule, or let him notice what needs doing.

  • Triage new errors

    Reproduces each new error on his computer, finds the commit behind it and files an issue with the fix he suggests.

    On his own
  • Review pull requests

    Mention him on a PR and he reads it, runs the tests and points out bugs and missing cases.

    When asked
  • Write the release notes

    Turns the week's merged PRs into release notes and posts them in #eng every Friday.

    On a schedule
  • Keep dependencies current

    Opens a PR for each outdated package every week, with its changelog and the tests passing.

    On a schedule
  • Watch the deploys

    Checks for new errors after each release and tells its author in Slack if something broke.

    On his own
  • Explain the code

    Answers how a part of the codebase works, with links to the files and PRs behind it.

    When asked
  • Sort customer feedback

    Groups the week's requests into themes and links each to the issue it belongs to.

    On a schedule
  • Draft specs

    Turns a thread or a call's notes into a spec, with the open questions for the team.

    When asked
  • Keep the roadmap current

    Notices issues that slipped past their cycle and asks their owners for an update.

    On his own
  • Summarize user interviews

    Pulls the quotes, problems and requests out of each interview into your research doc.

    When asked
  • Write the weekly update

    Shares what shipped, what slipped and what's next in #product every Friday.

    On a schedule
  • Check designs against the spec

    Compares the Figma file with the spec and lists the gaps before handoff.

    When asked
  • Prep for every call

    Sends a brief on the account and its open deals an hour before each meeting.

    On a schedule
  • Keep the CRM clean

    Logs notes and next steps after each call and moves the deal to the right stage.

    On his own
  • Send the pipeline digest

    Posts the deals that moved or stalled this week in #sales every Monday.

    On a schedule
  • Follow up after demos

    Drafts a follow-up with the recap and next steps right after each demo.

    On his own
  • Research new leads

    Looks up each new lead's company, role and recent news and adds it to the CRM.

    On his own
  • Answer security questionnaires

    Fills them in from your past answers and flags the questions he can't answer.

    When asked
  • Draft replies

    Drafts an answer to each new ticket from your docs and past replies, ready for an agent to send.

    On his own
  • Escalate bugs

    Spots tickets about the same bug and files one issue that lists every affected customer.

    On his own
  • Report on the week

    Shares ticket volume, the top issues and the slowest replies in #support every Monday.

    On a schedule
  • Fill gaps in the help center

    Notices questions your docs don't answer and drafts the missing articles.

    On his own
  • Look up an account

    Checks a customer's plan, invoices and recent errors before you reply.

    When asked
  • Close the loop

    Tells every customer who asked for a fix or a feature once it ships.

    On his own
  • Write launch content

    Writes the blog post, changelog entry and social posts for a release from its PRs and spec.

    When asked
  • Report on campaigns

    Puts the week's signups and leads in one sheet, with what changed since last week.

    On a schedule
  • Keep pages up to date

    Finds docs and pages that describe features you've changed and drafts the updates.

    On his own
  • Write the newsletter

    Drafts the monthly newsletter from what shipped and what the team wrote.

    On a schedule
  • Turn calls into case studies

    Drafts a case study from a customer call and the account's results.

    When asked
  • Track competitors

    Checks competitors' sites and changelogs and posts what's new in #marketing every week.

    On a schedule
  • Onboard new hires

    Creates their onboarding checklist, shares the right docs and answers their first-week questions.

    When asked
  • Screen applicants

    Sums up each new application against the role's must-haves for the hiring manager.

    On his own
  • Schedule interviews

    Finds a time that works for the whole panel and sends the invites.

    When asked
  • Answer policy questions

    Answers questions about leave, expenses and benefits from your handbook.

    When asked
  • Prepare review cycles

    Collects each person's goals, work and peer notes before reviews start.

    On a schedule
  • Plan around time off

    Posts who's out next week in each team's channel every Friday.

    On a schedule
  • Prepare the month's close

    Matches payouts to invoices and lists anything that doesn't add up.

    On a schedule
  • Collect overdue invoices

    Sends polite reminders for invoices past due and tells you who still hasn't paid.

    On his own
  • Chase missing receipts

    Finds card charges without a receipt and reminds the people who made them.

    On his own
  • Check spend against budget

    Compares each team's spend with its budget and flags anything off track.

    On a schedule
  • Answer revenue questions

    Pulls MRR, churn or a customer's billing history when someone asks.

    When asked
  • Update the company metrics

    Fills in the metrics sheet every Monday and posts what changed.

    On a schedule
  • Answer IT questions

    Walks people through VPN, laptop and account problems from your IT docs.

    When asked
  • Handle access requests

    Collects requests for tools, gets the owner's approval and logs who has what.

    When asked
  • Prepare offboarding

    Lists every tool a leaver can access and checks each account is closed.

    When asked
  • Find unused licenses

    Lists seats nobody used last month and suggests which to cancel.

    On a schedule
  • Watch for risky sharing

    Spots files shared publicly or outside the company and asks their owners about them.

    On his own
  • Track contracts

    Keeps the list of tools and contracts current and warns a month before each renewal.

    On his own

He works the way your team does

His own computer, the apps your team already uses, and the places you already talk. Connect an app once for everyone, or just for yourself.

  • Slack
  • GitHub
  • Linear
  • Gmail
  • Google Drive
  • Google Sheets
  • Notion
  • Jira
  • HubSpot
  • Stripe
  • Intercom
  • Salesforce
  • Zendesk
  • Figma
  • Asana
  • Airtable
  • Excel
  • Word
  • @Eduard summarize feature requests from Intercom and turn the top three into Linear issues

Teach him once and the whole team benefits. Eduard learns from the way your team already works with him, and what one person teaches him, everyone gets.

He remembers what he learns. Skills you teach him, preferences you mention and what comes up in conversations.

Your accounts and DMs stay yours. Apps you connect yourself, and what you tell him in a DM, are used only with you.

He never sees your credentials. You sign in to your apps yourself, so he never gets a password or a token.

Nothing important happens without your approval. He suggests and someone on the team decides. Initiatives need a yes before he starts. Sensitive actions need one from the person who asked, or an admin.

One plan for your whole team

Team

$20per organization / month

  • His own computer with a browser
  • Works in Slack, GitHub and Linear
  • 1,700+ integrations
  • Initiatives and automations
  • Shared memory and skills
  • Approvals for sensitive actions
Hire Eduard for your team

Questions

How is Eduard different from ChatGPT or Claude?

They're personal assistants: each person has their own, and what you teach yours stays with you. Eduard is one coworker for the whole company. He works in your shared channels, suggests work and follows through on it, and remembers what the team teaches him.

Does he do things without asking?

He suggests initiatives and starts one only after someone approves it. Sensitive actions need an approval every time.

How does he decide what to suggest?

From what happened since yesterday in the channels, repositories and Linear teams he's part of, and from what your team has taught him matters.

What can I hand him?

Research, reports, spreadsheets and documents across your apps, bug fixes and pull requests, code review, issue triage, and anything that should happen every week.

Does he need access to everything?

No. He starts with Slack alone, you connect apps one at a time, and the accounts you connect yourself are used only in your own DMs.

What happens if we remove him?

Uninstall him from the web app. Deleting your workspace removes him everywhere, disconnects every account and deletes what he learned.

Give your team an AI employee who takes initiative

Add him where your team works, and tomorrow morning he'll have his first suggestions.

Hire Eduard for your team