An AI revenue team that researches your market and drafts your outreach. With a seat, approve a customer profile tonight. By morning you have up to 10 companies researched with the reason each one fits, up to 5 contacts with the evidence for each address, and drafts ready for you to review.
Every email leaves your own mailbox under your name, only after you approve it. Replies too. It is not for anyone who wants outreach sent unread.
One workspace. 9 AI roles.You review the work.Runs on your own AI key and Gmail. Contacts come from your saved records or your own Apollo account.
Three decisions. Your next move is ready.
Meridian Labs fits your customer profile. Review the account research and the first message your team prepared.
Review the draft →You built the product and you run every sales conversation. Choosing who to sell to, finding the companies and the right person, and writing the first email all wait for a free evening. You approve who to target. The roles research those companies and draft the first emails, and you send them.
The first run reads your website, researches up to 10 companies and up to 5 contacts, and drafts an opening email for each contact it can source.
You confirm the brief, choose the profile, edit the drafts and send them from your own mailbox. The relationships and the commercial decisions are yours.
Already selling at a software company, with a quota and a book of accounts? The seller workflow has its own page →
Open Today for your next decision. Each draft sits beside the research it came from, so you can edit it in your own voice before it goes anywhere.
The reason it matches your profile and the source that named it sit beside the draft.
Use AI Assist to refine a draft. Apply or undo the suggestion.
Check the recipient, message and mailbox. Approval places the draft in your Gmail; you press send there.
Meridian Labs · Fictional account
Paste your website. You get a business brief with the source behind each section and a short list of what it could not read. Correct it and confirm.
Explore the business brief →Market research proposes up to three customer profiles. Approve one, and the first run researches up to 10 companies and 5 contacts, with the evidence for each.
Explore account research →Approve a draft and it lands in your Gmail drafts. With Attio connected, a daily plan adds up to 5 companies a day and pauses while 25 drafts wait for you.
Explore your working day →The brief and the market research need only your website. Drafts need a connected Gmail. The daily plan saves companies and contacts to Attio, and contact lookup uses your own Apollo account only when you turn it on.
Explore connection setup →Attio and Apollo are marked Preview in Connections, which means we built the connection from the vendor's documentation and have not yet tested it on a live account. Check what each one does there before you connect it.
Go-to-market and sales development have work from your first day. The customer roles wait until you have customers, and say so. Open a role to see its work, where that work goes next, and the decisions that stay with you.
Each company carries the reason it fits and the source that named it. A company it cannot confirm from its own website is held back.
Inspect an account →You see the exact message, recipient and mailbox. Before a draft reaches Gmail it is checked against your exclusion list, and a match is held with the reason.
Inspect an approval →Follow action receipts. An uncertain result stays visible for review before another attempt.
Inspect a receipt →Start on one seat. When you hire your first salesperson, add them on a seat at the same price and assign them roles. They pick up the brief, the research and the conversations already in progress.
Review pricing and usage →$99 / person / month
Billed monthly. All nine roles included.
Your AI provider and optional enrichment provider bill usage separately. Review allowances and limits before activating. Bring your own AI provider key.
You can run the audit on your own site first. It needs no account.
Read the getting-started guide →Founders who sell their own product and have not made a first sales hire. You keep the judgment and the send; the roles do the research and the drafting.
No. You set the direction, approve customer-facing work, and own the relationships and the commercial decisions. The roles prepare the brief, the research, the drafts, the follow-up and the reviews around you.
Point it at your website and it drafts a brief of your business for you to correct and confirm. Then it researches your market and proposes customer profiles; you approve one, and it researches the first companies and contacts and places addressed drafts in your own Gmail. You read, edit and send. Connect Attio and the daily plan keeps a small batch arriving.
No. The brief and the market research need only your website. Drafts need a connected Gmail; the daily plan also needs Attio as the CRM; contact enrichment uses your own Apollo account only when you turn it on. Customer and pipeline roles wait for customers and a pipeline to read, and say so.
No. It helps you run the work that can create opportunities. Product fit, your offer, the buyer and your own follow-through decide the result. The record keeps drafts written, emails sent, replies, meetings and opportunities as separate counts.
Your seat includes nine roles that share one confirmed brief: research, outreach preparation, deal work, customer care and leadership. You choose who owns each role and control its tools and sending permissions, and review the exact action before approving an external send. Onboarding places drafts in your mailbox for you to send yourself.
Add them to your team and assign one or more roles. They inherit the brief, the research, the conversations and the history in progress. Assigning responsibility does not remove another holder or share private drafts.
A seat is $99 per person per month, or $1,089 a year for a month free, and holds all nine roles. There is no free tier and no trial: a seat is what starts the schedule. Before you buy, you can run the audit on your own site with no account. Those runs share a fixed daily budget; when it is used up, we save your request and email the result after it resets at 00:00 UTC. When you hire, you add a seat at the same price. If a seat lapses, scheduled runs stop and your data stays as it is.
Yes, and it is step one of setup. The seat buys the roles, the schedule and the software. The model calls run on a key you supply (Anthropic, OpenAI, OpenRouter or Amazon Bedrock) and that provider bills you directly, so we never mark up inference and never meter how much you write. One key covers every role you hold. Contact enrichment, when you turn it on, spends credits from your own Apollo account.
The work runs on our servers, so we process what it needs: the brief, the research, and the CRM, email and calendar you connect. Encrypted in transit and at rest, used only to produce your work, never sold and never used to train models.
Start with your website. You confirm the brief and pick the customer profile, the roles research and draft, and you send.
Start with your business ↗A seat starts the schedule. Your own AI key runs the work.Turn the business behind your website into a focused plan for finding the first customers.
A clear offer and buyer profile give account research and outreach a useful direction, which is how this role helps reduce time spent on companies whose needs do not match what you can deliver. It creates no revenue on its own.
Starts with your URL. The first launch reads your website, proposes a business brief in eight sections with the source behind each, and asks only for what it could not read. If your site describes a concept rather than a launched product, the brief keeps the hypothesis separate from what you can sell today. Once you confirm the brief, market research runs on web search and returns a market estimate with its method, assumptions and sources, or says the estimate is not established, plus up to three customer profiles.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
A founder pastes their URL. The brief comes back naming a service-team buyer and an operational problem the product addresses, with two claims marked as needing proof. After confirmation the market step returns two profiles, each with six candidate companies and the source that named them, and one profile is approved for research.
A scenario to show the shape of the work, not a customer result.
Confirm what you sell, what is available today and who you want to help. Answer the focused questions the brief could not settle: geography, exclusions, pricing, proof. Approve a market profile. Material changes to the brief are proposals you accept or reject; once confirmed, the brief is reused everywhere and no role asks for it again.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
A reviewable market and offer hypothesis that can produce a first researched account batch. Over time the profile should get more specific as real replies replace assumptions.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: An approved customer profile and the confirmed brief.
What happens next: Research companies and contacts that match it.
What moves: The offer, the buyer problem and the claims you can support.
What happens next: Prepare replies and deal conversations from the same facts.
What moves: The commercial assumptions behind the plan.
What happens next: Compare them with what the pipeline and payments say.
Useful from the first minute, because it needs only your website. Market recommendations stay hypotheses until evidence supports them. It cannot validate demand, product readiness or willingness to pay from a website, and a research call runs within a per-launch ceiling of AI calls and web searches.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Your sales development role prepares account research and outreach for your review.
This role builds the top of the pipeline by finding a reason to contact each company. Better targeting and contact evidence reduce wasted outreach and put your time on the conversations that matter. Replies and meetings are outcomes to track, not something research alone can promise.
Uses the confirmed brief and the profile you approved. The first launch researches up to ten companies, each with a source from its own website, and up to five contacts, checking your saved contacts first and using your own Apollo account only when you turn that on. After the first batch, a daily plan can keep going: up to five new companies a day, saved to your CRM, with a draft per contact.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
A company brief shows why a firm matches the approved profile and cites its own careers page. An operations lead is found in your saved contacts, so no enrichment credit is spent. A draft about the problem named on their site lands in your Gmail. You send it; the reply stops the follow-up clock and shows up on Home as a conversation to take.
A scenario to show the shape of the work, not a customer result.
Review the first company batch and correct the profile if it is off. Decide whether the plan may spend your Apollo credits, connect Gmail for drafts and Attio for the daily plan, and take over any conversation that gets a reply. Once the profile is approved the plan reuses it; you are never asked to research a company yourself.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
An accepted target list and a steady flow of drafts you can explain. Positive replies and meetings are the outcomes to measure, and the record keeps them separate from drafts written and emails sent.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: A reply, with the company, the contact and the outreach history.
What happens next: Carry the conversation on without asking the buyer to repeat themselves.
What moves: Companies held back, corrections to fit, and repeated objections.
What happens next: Sharpen the profile and the opening message.
What moves: Prospecting activity and where it stalls.
What happens next: Name where targeting or follow-through needs attention.
Needs a confirmed brief and an approved profile. Drafts need a connected Gmail with draft permission; the daily plan also needs Attio as the CRM and Gmail read access to see sends and replies. Enrichment needs your own Apollo account and explicit consent, and spends within daily ceilings. A found address is not proof of employment, deliverability or permission to contact.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Help you turn buyer interest into a qualified opportunity, a clear next step, and a well-supported buying decision.
This role keeps interested accounts moving through the commercial process and stops quiet deals from disappearing. Negotiation, commitments and the relationship stay with you.
Receives replies and researched companies from Sales development, or reads the opportunities and contacts in the CRM you connect. It keeps the confirmed brief behind every draft, so a reply reflects what you sell and what you can claim.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
A buyer replies asking about rollout. The role drafts a reply, asks the sales engineer role for a supported answer on the integration question, and records a proposed next meeting. The opportunity stays at its current stage; a reply is not a win.
A scenario to show the shape of the work, not a customer result.
Lead the customer conversations that matter, approve pricing and commitments, and decide whether an opportunity is qualified. Set the approval scope: one message, or a defined follow-up sequence. The role prepares the context and the routine follow-through so your time goes to the decision.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
Opportunities with current context, a named owner and a visible next action. The commercial aim is more qualified deals moving toward a decision; whether they close depends on the buyer and the offer.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: A technical question and the deal context.
What happens next: Answer from supported material, or say what is not supported.
What moves: A confirmed sale, the buyer goals and the commitments made.
What happens next: Prepare onboarding so nothing promised is lost.
What moves: Opportunity changes and the evidence behind them.
What happens next: Inspect pipeline quality and what needs attention.
Most useful once replies or opportunities exist. Sending needs a connected Gmail (verified) or Outlook (preview) and the send layer turned on; opportunity updates need a connected CRM. It cannot commit you to pricing, terms or delivery outside the scope you approved.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Help buyers understand whether your product solves their technical problem, using answers your team can stand behind.
Technical uncertainty stalls buying decisions. This role helps you answer accurately, prepare relevant demonstrations and expose product gaps before they turn into commitments you cannot keep.
Uses the product facts from your website and the confirmed brief, then the documentation, proof points and evaluation notes you add. An unknown capability stays unknown until you confirm it; the role never fills a gap with a guess.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
A buyer asks whether the product writes to their CRM. The role links the supported read actions, points out that the write action they need is not supported, and drafts a reply that says so, instead of treating a connector name as proof that every action works.
A scenario to show the shape of the work, not a customer result.
Confirm product behaviour the documentation does not settle. Approve technical commitments, decide whether to close a gap or decline a poor-fit evaluation, and run the demonstrations that need live access. The role prepares; you validate.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
Better-informed technical decisions and fewer evaluations that stall on an unanswered question. The commercial effect is surfacing poor fit early and reducing avoidable technical delay.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: A supported answer, an evaluation result, or an explicit gap.
What happens next: Update the deal plan and the reply to the buyer.
What moves: Recurring technical needs and objections.
What happens next: Refine positioning and prepare content that answers them.
What moves: A technical win, and the enablement material a partner needs.
What happens next: Reuse the proof with partners instead of answering the same question twice.
What moves: Evidence of a product limit that affects buyers.
What happens next: Choose the product or commercial response.
Needs technical source material and a real question or evaluation. Evaluation records are entered by hand today; no integration feeds them. It does not invent certifications, validate security claims on its own, or promise roadmap features.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Find and prepare partner opportunities that can open customer conversations beyond your direct outreach.
Partners can bring access, trust and complementary capability. This role organises that route so a potential introduction becomes accountable work rather than a list of partner names.
Uses the offer and target market from the confirmed brief. It adds partner profiles, account overlap and relationship evidence as you connect them; overlap data comes through a partner-data connector that is still in preview.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
The role finds an implementation partner serving the approved buyer segment, prepares a mutual-value brief, and proposes an introduction request for one shared account. It does not imply the partner has agreed, or that the shared account is already an opportunity.
A scenario to show the shape of the work, not a customer result.
Choose the partner strategy, approve every outreach and introduction, and own the partnership terms. Confirm what may be shared with a partner. The role gathers context so each partner conversation does not start from zero.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
A small set of credible partner relationships and shared opportunities with visible ownership. Revenue contribution is measured through partner-sourced or influenced outcomes, not assumed.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: An accepted introduction and the shared-account context.
What happens next: Work the opportunity with a clear owner.
What moves: Partner enablement needs and technical questions.
What happens next: Prepare accurate technical material once, for reuse.
What moves: Partner activity and attribution evidence.
What happens next: Judge whether the partner motion deserves more investment.
Useful when the offer benefits from a partner motion and there is partner data to read. Partner certification and enablement records are entered by hand today; overlap data needs the partner connector, which is in preview. It cannot create partner consent, guarantee an introduction, or share account information beyond the scope you approve.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Help you keep the customers you win, understand whether they are getting value, and prepare expansion conversations you can justify.
The first sale becomes more valuable when the customer adopts, renews and has a reason to expand. This role carries the goals promised during selling into the work after purchase.
Receives the buyer goals and commitments from the sales handoff. It adds CRM, billing, support and success-platform signals as you connect them; without customers it explains the setup it needs and stays quiet.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
A customer's adoption falls while a support issue stays open. The role proposes a recovery conversation and asks the sales role to hold the planned expansion message until the issue is understood.
A scenario to show the shape of the work, not a customer result.
Confirm customer goals, own the relationships that matter, and decide on concessions or commercial changes. Review each proposed action. The role assembles the evidence so you are not reconciling usage reports and support threads by hand.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
Visible customer needs and timely actions that support adoption, retention and expansion where it is earned. A health score is a signal, not proof a customer will renew.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: A customer risk that needs an issue resolved.
What happens next: Coordinate the response and bring the resolution back.
What moves: A supported expansion need or a renewal conversation.
What happens next: Prepare the commercial next step.
What moves: Customer outcomes and recurring needs.
What happens next: Improve targeting and the proof the site can use.
Needs actual customers and connected customer signals: a CRM, and where you use them a billing account and a support or success platform, several of which are in preview. Before those exist it can explain the setup and prepare a handoff template; it will not manufacture a health report.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Help you respond to customer issues with context and make those issues visible to the rest of the revenue work.
Unresolved issues damage trust, renewals and active evaluations. This role helps coordinate accurate responses and keeps a sales or expansion message from ignoring a customer's current experience.
Uses the support conversations you connect, your approved help material, and the account's business and customer history. It becomes active when there are issues to assess and says so when there are none.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
A trial account reports a blocker. The role drafts a response from approved documentation, alerts the deal owner, and notes that the planned follow-up message needs to acknowledge the problem before it goes out.
A scenario to show the shape of the work, not a customer result.
Handle exceptions, confirm uncertain answers, and assign the technical owner where needed. Approve customer-facing replies within the scope you configured. Product fixes remain with the product or engineering team.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
Faster access to issue context and coordinated follow-through. The intended revenue contribution is protecting trust and reducing avoidable disruption to renewals and buying decisions.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: An escalation, or a confirmed resolution.
What happens next: Update the customer plan and retention priorities.
What moves: A support issue on an account in an active buying conversation.
What happens next: Adjust the timing and wording of the next message.
What moves: A reproducible product question or gap.
What happens next: Validate the answer and describe the real remediation.
Needs support records and approved knowledge. The support connectors (Zendesk, Intercom) are in preview until verified against a live account. It must not call a ticket resolved because a response was drafted, invent a service level, or promise that it can fix product defects.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Help you see where the sales process is stuck and decide which selling work needs attention next.
As prospecting and deals accumulate, more activity does not mean better progress. This role inspects the evidence so you can improve targeting, follow-through and deal quality before adding management headcount.
Uses the confirmed direction, prospecting activity, opportunity history and whatever conversation evidence is connected. For a solo founder it reviews the motion as it is, rather than pretending a team already exists.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
Research is producing accepted companies, but interested replies are waiting days for a response. The role highlights that delay and recommends fixing the response step before increasing outbound volume.
A scenario to show the shape of the work, not a customer result.
Decide which process changes to adopt and where your limited selling time goes. Review exceptions rather than every record. When people join, they keep responsibility for their own decisions and performance.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
A clearer view of what blocks pipeline progression and a practical order for fixing it. The intended effect is a more disciplined motion and better use of your time.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: Evidence-backed priorities and where prospecting stalls.
What happens next: Adjust research or follow-through where the motion is stuck.
What moves: Patterns in acceptance, objections and qualification.
What happens next: Revisit the profile or the message.
What moves: Pipeline quality and capacity constraints.
What happens next: Inform revenue planning and hiring decisions.
Needs enough real activity to inspect: opportunities in a connected CRM and some history. With little history it reports limited evidence and the setup gaps, rather than confident performance judgements.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Help you connect revenue evidence, spending and capacity to the next business decision.
This role reads across acquisition, selling, retention and partnerships to help you decide which motion deserves more effort, which costs need attention, and when a human hire has a clear job to take over.
Uses the confirmed commercial assumptions first, then your own opportunity, payment, usage and cost evidence as you connect it. A concept-stage business gets an assumptions-based plan, not an invented revenue forecast.
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
One profile produces replies but little qualified pipeline; another yields fewer conversations with stronger fit. The role compares the evidence and the cost of each and proposes where the next campaign should focus.
A scenario to show the shape of the work, not a customer result.
Set the business goal, budget constraints and planning assumptions. Decide on hiring, pricing and spending. The role prepares the analysis and shows what is missing so you can act without stitching reports together.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
Better-informed choices about growth, retention and capacity. The aim is to invest in work that contributes to revenue and to hire when the evidence shows a real job, rather than to treat a forecast as a guarantee.
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
What moves: Evidence of which profiles and offers are working.
What happens next: Revise market priorities and campaign hypotheses.
What moves: Revenue priorities and capacity constraints.
What happens next: Translate the plan into sales work and coaching.
What moves: A sourced decision brief with assumptions and alternatives.
What happens next: Choose the next investment, experiment or hire.
Revenue analysis needs your own commercial data: a CRM with amounts and stages, and a billing connection for collected cash. Your subscription to this product is never counted as your revenue. Attribution and forecasts stay limited by the evidence and the method used.
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.