Conversations. Not another sequence.
Overture finds the account, researches it, writes the email and puts its own draft through a quality gate it cannot skip. Only what passes is sent, and only to recipients for whom you have a legal basis on file. You are needed only when it escalates.
You have enough sequence tools.
Sequencers have been judged on whether the email goes out, not on whether they know anything about the account. That is the wrong yardstick for a tool writing in your company's name.
A sequencer gets the email to the right list at the right time. What is actually happening inside the account stays outside it.
{{first_name}} and {{company}} say nothing about the account. Real personalisation names something the account is actually doing.
A no gets logged, the sequence carries on, and nothing learns from it. The next touch repeats the same mistake.
Not a funnel. A loop.
A sequence ends at the last touch. Here nothing ends: the classification of every reply flows back into the model, and the weights are re-tuned weekly.
Account, contact, sector, market and touch: the objects any outreach consists of.
Five enrichment stages, from the website to public sources, feed the ICP score.
Deterministic checks run before anything is released for sending. A draft that fails them is never put forward for release.
What the gate cannot resolve goes to a queue for a person. Nothing carries on unnoticed.
As of 2026-08-06
As of 2026-08-06
As of 2026-08-06
As of 2026-08-06
The loop is why a no is not wasted. The reply's classification feeds the same weights that decide the next sector, the next touch and the next variant.
One draft, worked through.
Rather than claiming the system checks its own work, here is the whole path from research to the gate verdict. Every step names its source.
Nine sectors rotate per market. This match comes from the running search and falls in the manufacturing sector, DACH market.
HTML ingestion, Apollo person/org match, social-media scrape, web signals, LLM synthesis. Each stage writes its own field; none overwrites another.
Employee count against the target band, operational-complexity keywords, signal and penalty terms. The score sets the order, not the decision.
The model selects an angle for the sector and a text variant of the template, which is continuously tested against the others. Both are logged.
Deterministic checks first: length, greeting, spam patterns. Then weighted model criteria: tone, personalisation, CTA clarity, language quality, claim integrity. The first draft failed on claim integrity and was redrafted once. A second attempt is allowed, a third is not.
“Second draft clears the gate: tone, personalisation, CTA clarity, language quality and claim integrity all pass. Whether and when it is sent is your decision. It is sent only to recipients for whom you have a legal basis on file.”
That is the difference from a sequence. A sequence sends on schedule whether the text holds up or not. Here there is a checked draft, ready for release, and every step behind it can be read back.
Deterministic rules first, then weighted model criteria. The two together produce the verdict, never the model alone.
The language model. Whether the draft passes the gate is not its own call.
Illustration of the send path, not a log of an actual send. Account, contact, email body and outcome are invented; the account is described by category only: a mid-sized manufacturer, DACH, around 140 employees. The order of the steps matches the implemented pipeline.
Where the boundaries are drawn deliberately.
Cold email is tightly regulated in Germany. That is part of the product, not the fine print at the end.
Your company is the sender and the controller. Overture runs the campaigns you release; the decision whether and to whom to write stays with you.
Commercial email to an account not yet contacted needs the recipient's prior express consent, § 7(2) No. 2 UWG. No B2B exception exists for that.
§ 7(3) UWG allows advertising without consent only to existing customers, for the sender's own similar goods or services, and only where the customer was told of the right to object both when the address was collected and on every use. A newly researched account does not qualify, by definition.
Every message names your company as sender and carries a valid address to which the recipient can send a demand that further messages stop. § 7(2) No. 3 UWG requires both, independently of the consent question. The unsubscribe is then stored as a hash and checked before every further send; the registry alone does not satisfy the statute.
Researched contact data is personal data. Art. 6(1)(f) GDPR can carry the research and the scoring. It cannot carry the commercial send itself while the consent required by § 7(2) No. 2 UWG is missing. Under the Datenschutzkonferenz guidance on direct marketing, the legitimate interest falls away at the outset wherever unfair-competition law bars the contact channel. The Art. 14 GDPR information duty applies regardless and falls due within one month at the latest. The legal basis and the Art. 14 information are your company's responsibility as controller.
Every unsubscribe is stored as a hash of the email address, never in plain text, and checked before every further send.
Processing runs through EU endpoints. Whatever the gate cannot resolve goes to a person.
Overture does not research established large enterprises or well-known SaaS vendors. Outreach targets mid-sized accounts that fit the ICP.
Two ways to run it.
Containerised, deployed in your own cloud, documented and handed over. You own and operate it.
Planned, not yet available. The intention is a classic subscription: sign up online, pay, run the process from one interface. No launch date is fixed.
Frequently asked.
No. A sequencer schedules the send. Overture researches the account through five-stage enrichment, writes the draft and checks it against a gate built from deterministic rules and weighted model criteria. What gets sent is what you release, and only to recipients for whom you have a legal basis on file.
For a deployment in your own cloud, your company is the sender under § 7 UWG and controller under Art. 4(7) GDPR. After handover, Studio 073X e.K. has no access to the running system. This does not carry over unchanged to the planned Cloud variant: there, Studio 073X e.K. would process on your behalf, which requires a data processing agreement under Art. 28 GDPR; and to the extent we co-determine the purposes and means of the research, joint controllership under Art. 26 GDPR comes into play. The allocation of roles follows from the actual circumstances, not from this description.
For the send, yes, as soon as it is commercial email to a company you have not contacted before. § 7(2) No. 2 UWG requires prior express consent with no B2B exception, and the narrowly drawn existing-customer exception in § 7(3) does not reach a newly researched account. Research and drafting are separate: that is data processing under Art. 6(1)(f) GDPR and requires no consent. Consent is the barrier before the send, not before the draft.
It is redrafted once. If the second attempt also fails, the case goes to a queue for a person instead of running on automatically.
Every opt-out is stored as a hash of the email address, never in plain text, and checked before every further send.
Overture does not research established large enterprises or well-known SaaS vendors. Outreach targets mid-sized accounts that fit the ICP.
Yes. Deployment is the containerised variant in your own cloud, documented and handed over. Cloud is the planned subscription variant with a dashboard, not yet available.