Research eats selling time
Reps spend the morning reading websites and old notes instead of talking to buyers.
For revenue teams
Research the account, personalise the first line, summarise the discovery call, update the CRM. Let models do the busywork so your reps spend their day selling.
account briefs before the next call
first lines grounded in your notes
call notes summarised and structured
The problem
Reps spend the morning reading websites and old notes instead of talking to buyers.
Merge tags are not personalisation. Prospects can tell, and reply rates show it.
The discovery call was great. The record says 'good call, follow up'.
Capabilities
Send your notes and public context in the prompt and get a one-page brief with likely priorities and questions.
Generate a tailored first line for every contact in a sequence, priced per call so you know the cost per touch.
Ask for JSON with next steps, objections and stakeholders, ready to post into your CRM fields.
Automatic fail-over means a busy model does not stall a batch of outreach.
Every response carries its price, so your workflow can log what each email, brief or summary cost.
Route formatting and classification to the lowest-priced chat model, and save heavier models for strategy.
Use cases
A tight summary of the account, open opportunities and the questions to ask.
First lines and P.S. notes written from what you actually know about each prospect.
Pain, budget signals, timeline and next steps pulled from your transcript.
Suggested responses to common pushback, written in your team's voice.
How it works
Paste call notes and see the summary, tokens and price instantly.
Call the endpoint from your CRM workflow or automation tool with a bearer key.
Watch daily and month-to-date usage in the console as more reps lean on it.
Control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'No. You decide what goes into each prompt, typically via your own workflow or automation tool, and the model works only from that.
Ask for JSON or a template in the prompt. Many teams map the result straight into CRM fields.
Each response includes its exact price, and the catalog shows per-token prices for every model before you call.
Accounts have a requests-per-minute rate limit you can set in settings, and every call is visible in history.
Start free, measure cost per touch, scale with the pipeline.