ConvertOnly: from an ad template to a booked callback, without a marketing team

Small businesses know that ads work. What they do not have is the time to configure a campaign or the discipline to chase a lead within the ten minutes that decide whether it answers. ConvertOnly, built as Alnitak's own product, is one platform for both halves: pick an industry template, adjust the creative, launch the campaign into the advertising platform with one click, receive the leads through webhooks, and let an AI voice agent call each one, record the outcome and book the callback. A multi-tenant Rails 8 backend with subscriptions, a Next.js dashboard, and a CRM sync. It was built and demonstrated and never launched to paying customers, which is stated here because it changes what you should believe about the rest of the page.

What changed, measured

1. One clickFrom industry template to a live campaignCampaign, ad set and ad created in the customer's own advertising account through the Marketing API, with the lead form attached and the identifiers tracked.
2. Every leadCalled, not queuedThe voice agent calls each lead and stores the transcript, the sentiment, the summary, whether it reached voicemail, and the callback time the person asked for.
3. One row per stepAd, lead, call, callback, CRMEach handoff writes a record a person can read, so nothing between the click and the conversation is invisible or has to be reconstructed from three dashboards.
4. ZeroPaying customersIt was built and demonstrated and never launched. No cost per lead, conversion rate or revenue figure is claimed here, because none was ever measured.

What it is built to produceBuilt to close the gap between an ad click and a human conversation, so a lead is spoken to while it is still warm instead of ageing in an inbox. This is the shipped proof for the workflow automation Alnitak sells to operators; the outcome numbers will come from a client's own signed baseline, not from this build.

Two people, one leak

The product research named two buyers. The small-business owner, with limited time, limited marketing knowledge and no appetite for becoming a media buyer, who wants the phone to ring. The marketing manager, with manual processes and several tools that do not speak to each other, who wants campaign management and lead tracking in one place.

Both were already spending money on ads. Both were losing the leads afterwards. That is the leak worth engineering against, and it sits after the part everyone optimises.

Where the money actually goes

A lead form submitted at nine in the evening is worth a fraction of what it was worth at nine in the evening if it is first read at eleven the next morning. Nothing about that is a marketing problem. It is a handoff problem, and handoffs are software.

So the architecture follows the handoff rather than the funnel diagram. A Rails 8 API holds the business logic, the integrations and the scheduled jobs. A Next.js dashboard gives the customer the interface. Accounts are multi-tenant with invitations, roles, API keys and plans, billing runs through subscriptions, and sign-in uses the platform account because the advertising account is the platform account. Records carry an audit history and a notification stream, so a disputed lead has a paper trail.

From template to live campaign

The customer picks an industry and a location, chooses a template that already carries the campaign objective, the audience defaults and the creative placeholders, adjusts the text and the images, and launches.

The platform then creates the campaign, the ad set and the ad inside the customer's own advertising account through the Marketing API, attaches the lead form and tracks the identifiers. Insights are fetched on a schedule and shown per campaign. The customer never sees an ads manager, which is the point: the product sells the absence of one.

From lead to call to booked callback

A submitted lead form arrives through a webhook, is signature-verified, and is mapped field by field into a lead record. Where the sector needs it, a property interest is attached and the lead is synced to the CRM the sales team already uses.

Then the voice agent calls. Call started, ended and analysed events arrive by webhook; the analysed event yields a call summary with the transcript, the sentiment, the summary, whether the call succeeded or hit voicemail, and, when the person asked to be called back, the date and time. A callback is scheduled with a retry count. Every step is a row someone can read, which is the difference between an automation you trust and one you quietly stop using.

Why an unlaunched product is on this page

ConvertOnly was built as our own product and never launched to paying customers. We could have left it off the site. It is here, labelled, because the alternative is a case study page where every project mysteriously succeeded.

What it proves is narrow and real: the chain runs end to end, in production code, across four third-party systems that each fail in their own way. That is the pattern Alnitak now sells to operators. A form or an ad creates the lead, the CRM gets it with its source attached, a call happens, a record is written, a callback is booked, and the whole chain is instrumented. The same chain with a person approving what the model drafts is the workflow automation and sales assistant work on the services page. What ConvertOnly cannot tell you is what it costs you per lead. Only your own baseline can do that.

Key Features

• Industry templates carrying the campaign objective, audience defaults and creative placeholders, so the customer edits a campaign rather than designing one from an empty form
• One-click launch through the Marketing API: campaign, ad set and ad created in the customer's own advertising account, with the lead form attached
• Lead capture through webhooks with signature verification, mapped field by field into lead records, so a malformed or spoofed payload cannot quietly become a lead
• An AI voice agent that calls every lead, with call started, ended and analysed events ingested by webhook rather than polled
• A call summary stored per lead: transcript, sentiment, summary, success and voicemail flags, and the callback date and time the caller extracted from the conversation
• Scheduled callbacks with retry counts, property-interest records where the sector needs them, and a CRM sync so the lead reaches the system the sales team already lives in
• Multi-tenant accounts with invitations, API keys, plans and subscriptions, notifications, platform sign-in, and an audit history on records

Business Impact

ConvertOnly is the shipped proof behind three of the services Alnitak sells: workflow automation, where a form or an ad becomes a CRM record, a call, and a booked callback with every step an event; the voice half of voice to document, where a call becomes a transcript, a sentiment, a summary and a time on a calendar; and the integration work in the assistant services, where the advertising platform, the caller, the billing system and the CRM have to agree with each other. It is also why the analytics service exists: campaign, lead and call data land in one place instead of three tabs. No customer revenue or campaign result is claimed, because the product was built and demonstrated, not launched. What it proves is that the chain runs end to end.