The one-sentence definition of a qualified lead, written so a new hire could apply it.
afka uses analytics cookies to understand how visitors use the site. No ads, no data sales.
The working manual for setting a client team up with the afka sales agent: signal-driven pipeline work, CRM hygiene and outreach nobody sends without approving, configured for the whole revenue team with a rhythm that survives the quarter.
A small revenue team where the pipeline is real but nobody owns the grunt work: stages go stale, follow-ups slip, inbound leads sit for a day, and the CRM stopped being trustworthy months ago.
Your first working artifact is a table with four rows: who talks to the agent, and where. Draw it with the client in ten minutes, because approval routing and the outreach gate both hang off it.
The owner talks to the agent in Slack and by voice, and holds the autonomy dial.
The sales lead works inside the CRM and owns the approval line for anything a customer sees.
Every rep can write to the agent, or dictate to it, in the afka composer: a rep asking for research on an account is configuring nothing and getting a researched brief back.
The meeting agent joins the weekly pipeline call on Zoom, Google Meet or Microsoft Teams, and the commitments people make out loud become tasks with owners.
The approver receives every gated send in the approvals inbox and as a Slack card, and a decision resumes the work in under two seconds. The teacher accepts what the agent learns about the territory, the objections and the tone. The audit reader checks weekly that every CRM write carries its before and after. In a revenue team the approver for customer-facing sends should be the sales lead, not the busiest founder.
One sales agent inside the client workspace: connected to the CRM, the inbox and the calendar, keeping records clean, routing inbound leads on arrival, drafting follow-ups from the actual conversation, holding every send at the approval gate the team set, with the sales skill pack filled from your interview.
Guidance is plain language: the ideal customer, the tone of a follow-up, what a qualified lead means in this company. Guardrails are code: the categories that always wait for a person, the claims a draft may never make, the discount floor no message may cross. A guardrail beats any instruction, and when the layers disagree the more conservative action wins. The interview gathers exactly these answers, and they go straight into the pack:
The one-sentence definition of a qualified lead, written so a new hire could apply it.
The claims a draft may never make: pricing promises, delivery dates, competitor comparisons.
The discount floor, as a number, and the one person who may approve below it.
The number of silent days after which a deal counts as stale, and what happens then.
Connections run through managed connectors: a popup opens, the client authorizes their own CRM, inbox and calendar, and afka never receives a password. The connectors screen shows every connection's status, reconnect is one click, and disconnecting is revocation within one task cycle. More than three thousand apps are supported, so the stack the team already has is almost certainly covered.
Export the pipeline and count what is stale: deals with no activity in two weeks, leads never routed, fields never filled. These numbers are your before picture and the team sees them again on the week-four call.
A new workspace picks the sales function and produces a first finished artifact from seeded sample data in under a minute: a researched outreach draft with its sources attached. Show the loop before any real account is at stake.
Internal field updates can run on Auto from day one. Anything a customer sees, an email, a quote, a sequence, waits for a person. Write the discount floor and the banned claims into the guardrail layer and show the team that the line is enforced in code, not in the wording the agent is given.
Let the agent de-duplicate, fill the missing fields and flag the deals that look dead while the reps watch. A visibly cleaner pipeline in one session, with every change carrying its before and after in the audit log, is the artifact that sells the rest of the rhythm.
Agree the lead-routing rules, put the follow-up cadence on the calendar, invite the meeting agent to the weekly pipeline call, and leave the approver owning the send gate. Review the week-four numbers against the before picture you took in step one.
The deployment holds because the rhythm matches how a revenue team already works.
Daily, five minutes: the approver clears the send queue. Every draft arrives with the conversation it came from, so approving is reading, not writing.
Weekly, on the pipeline call: the meeting agent attends, every commitment becomes a task with an owner, and the team agrees what graduates to Auto. Internal hygiene first, customer-facing sends last, if ever.
Weekly, ten minutes: the teacher reviews what the agent learned from edited drafts, accepts the phrasing that worked, and rejects what drifted from the voice.
Reps ask sharper questions than founders. Give the real answers.
The approval line the team chose, enforced in code. Drafting is free and gated sends wait at that line. Nothing customer-facing goes out on day one without a person, and the graduation to Auto is the team's own weekly decision, per category.
Every write lands in the append-only audit log with before and after, so any change can be found and reversed with evidence. Bulk writes above the level the team set wait for approval by design.
With the pause button, and it is measured in fractions of a second. In-flight work drains cleanly, and disconnecting the CRM revokes access within one task cycle. The pipeline stays exactly as the log last recorded it.
The three situations you will actually meet: a connector shows reconnect-needed, one click repairs it; a draft is wrong in a way the teacher can name, which becomes a skill correction the next draft applies; and a deal needs a human conversation, which the agent flags rather than fakes. None of the three is an incident.
You earn 30 percent of the client subscription for twelve months from the first paid invoice, with first-touch attribution for 90 days. Your implementation fee is your own business and stays yours. afka publishes no income projections: the terms are the terms.
Not unless the client sets it so. Drafting is free; sending is an external action and waits at the approval gate. Nothing customer-facing goes out without the level the client chose.
A visibly cleaner CRM: duplicates merged, fields filled, dead deals flagged, inbound routed. It is work the team has postponed for months, done while they watch.
Every change lands in the append-only audit log with before and after, and the autonomy dial decides what the agent may touch without asking.
The program terms, the agreement and your link are on the deployer page.
The deployer program