Frequently asked
questions.

Falora is an AI-powered growth intelligence platform that connects to your marketing stack, CRM, and customer data to surface actionable growth opportunities. It combines proven methodologies from 6 years of hands-on growth experience with advanced AI to deliver strategic recommendations tailored to your business. Think of it as an operational brain that continuously analyzes your data, identifies patterns, and proposes experiments, so your team can focus on execution rather than analysis.

Most teams are up and running in under 30 minutes. Falora connects directly to your existing tools like HubSpot, Salesforce, Meta, LinkedIn, and Google Ads, and starts ingesting data immediately. You'll receive your first strategic insights within the first day, and the system gets smarter the longer it runs. There's no complex onboarding process or months of setup. Just connect, configure your goals, and go.

Absolutely. We use enterprise-grade encryption both in transit and at rest, and we never share your data with third parties. Your data remains fully yours. You can export or delete it at any time. We're fully GDPR-compliant and undergo regular security audits to ensure your information stays protected. We also offer data residency options for enterprise clients with specific compliance requirements.

Yes. Falora integrates with 50+ tools across your entire growth stack, including HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Ads, Google Analytics, and more. The platform is designed to work alongside your existing workflows, not replace them. For enterprise clients, we also offer custom integrations and API access to connect proprietary systems or niche tools specific to your industry.

100%. Falora operates on an 'AI proposes, you decide' model. Nothing goes live without your explicit approval. Every experiment, budget shift, content recommendation, and strategic pivot is presented as a suggestion with full context and reasoning. You stay in the driver's seat while Falora handles the heavy lifting of data analysis, pattern recognition, and opportunity identification.

A growth agency provides people and execution on a retainer. You're paying for their time, waiting for weekly reports, and working on their timeline. Falora is an always-on AI platform that works inside your existing stack 24/7, continuously learning from your data and surfacing opportunities in real time. It doesn't replace your team. It amplifies them by automating the analysis and strategic thinking that would normally take consultants weeks. The result: faster insights, lower cost, and a system that gets smarter with every data point.

A growth engine is a repeatable, data-driven system that continuously identifies, tests, and scales the most effective ways to acquire and retain customers. Instead of relying on one-off campaigns or gut feelings, a growth engine combines strategy, experimentation, and real-time analytics into a structured process. Falora builds this engine for you by connecting your data, generating experiments, analysing results around the clock, and adapting your roadmap based on what actually works.

No. While agencies can certainly use Falora to serve their clients more efficiently, Falora is primarily built for in-house teams. It gives CMOs, commercial leaders, and founders the knowledge and tools to create a profitable go-to-market strategy and implement it directly, without depending on external consultants or agencies. Falora puts the strategic intelligence inside your company, so your team stays in control.

Sometimes. In our benchmark of 11 Belgian and Dutch B2B deployments, 4 produced positive ROI within 90 days and 7 did not. The four that worked all shared three traits: an offer with a clear cost-of-inaction, a TAM above 5,000 accounts, and an existing brand presence in dark social. The seven that failed shared the inverse.

Functionally none. Both terms describe an AI-driven outbound system that prospects, drafts and (in some configurations) sends outbound messages. SDR (sales development rep) and BDR (business development rep) are interchangeable in most North American and European usage.

Germany's UWG and BGH case law impose stricter B2B consent and transparency requirements than most member states. The combination of inbox-saturation, AI-disclosure obligations under the EU AI Act Article 50 (effective August 2026), and German enforcement makes AI SDR deployments structurally harder in DACH than in BENELUX or France.

Keep human SDRs when your ACV is above €100K, your buying group has 10+ stakeholders, your TAM is below 2,000 accounts, or your offer requires research and relationship work that no agent can compress. Multi-threading enterprise deals is a human-relationship problem, not a throughput problem.

Pick one ICP segment of 500–2,000 accounts. Deploy the AI SDR for 30 days with weekly review. Measure cost per qualified meeting, cycle time from signal to first reply, and percentage of conversations escalated to a human. If all three are improving by day 30, scale. If two are flat or worse, kill or rebuild.

A copilot suggests; an agent acts. A copilot generates a draft email for a human to send. An agent executes a multi-step workflow under defined rules and only escalates to a human on flagged exceptions. Most B2B GTM tools that claim 'agent' functionality in 2026 are still copilots.

On the Falora maturity scale, HubSpot Breeze, Salesforce Agentforce and Apollo's AI SDR sit at Level 2 (partial autonomy: agent executes single tasks under human supervision). They generate, draft and act on individual atomic steps but do not orchestrate end-to-end motions.

Level 5 self-optimisation involving solely-automated decisions about individuals likely falls under Article 22 GDPR (right not to be subject to fully automated decisions with legal or similarly significant effect) and may trigger Annex III high-risk classification under the EU AI Act. In practice, EU-deployed Level 5 systems require meaningful human oversight at the strategic layer.

Three changes consistently move teams up a level: (1) consolidate tooling so one orchestrator owns workflow state; (2) move from synchronous human-in-every-step to asynchronous human-on-exceptions; (3) instrument every action with feedback data so the agent can be evaluated and re-trained.

Because vendors price at one level and deliver at another. Knowing your current level; and the realistic next level for your stack; is the difference between a productive 12-month rebuild and a Frankenstack of half-finished automations that produce no measurable lift.

Not categorically illegal, but Germany's UWG and BGH case law impose stricter B2B consent and transparency requirements than most member states, and the EU AI Act Article 50 disclosure obligation (in force August 2026) requires recipients to know they are interacting with AI. Combined, this makes many current AI SDR deployments non-compliant in Germany without explicit AI disclosure and B2B legitimate-interest documentation.

From August 2026, EU AI Act Article 50 requires that AI-generated content (including text generated and sent by AI agents) be detectable as AI-generated, with limited exceptions. For B2B cold email this practically means including an AI-disclosure line and ensuring the technical means of detection (e.g. watermarking metadata) are in place.

Pure lead-scoring on firmographic and behavioural signals is generally not Annex III high-risk. It can become high-risk if it materially determines access to a service or has legal/significant effect on the individual (e.g. denying credit, employment, or essential services). The boundary is set by the deployer's purpose, not by the technology itself.

Article 99 of the EU AI Act sets fines up to €35M or 7% of global annual turnover for prohibited-AI violations, up to €15M or 3% for high-risk and transparency violations, and up to €7.5M or 1% for incorrect, incomplete or misleading information to authorities. National competent authorities apply these fines proportionally.

Prohibited AI practices have been in force since February 2025. AI literacy obligations (Article 4) since the same date. General-Purpose AI obligations since August 2025. Transparency obligations including AI-content and chatbot disclosure (Article 50) from August 2026. Annex III high-risk obligations from August 2026, with the Digital Omnibus likely shifting some categories to December 2027.

A GTM engineering system is the integrated stack of seven layers; signal, identity, reasoning, orchestration, activation, measurement and governance; that turns market and product data into qualified revenue conversations under autonomous or semi-autonomous control. It is the architectural counterpart to the GTM engineer role.

A modern B2B GTM tech stack composes seven layers: a signal layer (Common Room, 6sense, RB2B), an identity layer (Clay, Cognism, Apollo), a reasoning layer (Claude, GPT, in-house models), an orchestration layer (Clay, n8n, Default), an activation layer (HubSpot, Lemlist, Outreach), a measurement layer (Dreamdata, HockeyStack), and a governance layer (compliance, audit, EU AI Act conformance).

Top-quartile autonomous GTM teams in our portfolio use 8 tools across the seven layers; the median scale-up uses 23. The number that matters is not how many tools you have, but how many of them an orchestrator can read and write to in a single workflow.

A Frankenstack is a stack of 20+ point tools, none of which talk to the others, all of which produce dashboards nobody reads. Avoid it by choosing one orchestrator that owns workflow state and treating every other tool as a service the orchestrator calls. Consolidation typically reduces tool count by 50–70% in our rebuild engagements.

Falora sits primarily in the orchestration and governance layers, with native integrations into the signal, identity, reasoning, activation and measurement layers. Falora's role is to be the single orchestrator that reads from your existing best-of-breed tools, executes the autonomous workflow, and exposes the audit trail for EU AI Act compliance.

A GTM engineer owns the data, signals, agents and workflows that connect marketing, sales and product. Day-to-day this looks like building enrichment in Clay, automating signal capture from product usage and dark social, deploying AI agents for outreach, and instrumenting attribution as code rather than as dashboards.

In Europe, GTM engineers earn €75K–€140K base depending on stack ownership and seniority; in the US the range is $130K–$220K base. The role compounds value because one engineer typically replaces the workload of 1.4 marketing roles plus a junior SDR.

Below €2M ARR most teams don't need a dedicated GTM engineer. They need a marketer who is fluent in Clay, n8n and one autonomous platform. From €5M ARR upwards the dedicated role typically pays back within two quarters.

Clay accelerated the term but did not invent the discipline. The role exists because of three independent forces: AI agents collapsing software cost, the death of MQL-based pipeline, and dark-funnel buying behaviour. Clay is one tool inside a much larger stack.

The role survives precisely because of the AI agent wave. Agents need a system designer; someone who decides what signals matter, which workflows trigger which agent, and how human intervention is routed. That is what a GTM engineer does.

Outbound agencies in Europe charge €8K–€25K per month for retainer engagements, €350–€800 per booked meeting on per-meeting models, and €1,200–€2,800 per qualified opportunity on per-SQL models. Across 12 anonymised B2B scale-ups in our data, median total cost was €18K per month for 4 qualified meetings.

For most mid-market B2B SaaS scale-ups with €3M–€20M ARR, the unit economics no longer work. The agency model is structurally squeezed by sub-1% reply rates, 75% buyer preference for rep-free buying, and the deflationary pressure of AI tooling on the per-message cost. Some specialised use cases (enterprise outbound to named accounts, complex compliance markets) still favour an agency.

In our 12-company benchmark, AI-platform-driven outbound delivered a median cost per qualified meeting of €380 versus €4,500 for agency-managed motions; a 12× reduction. Time to first booked meeting dropped from 6 weeks (agency onboarding plus ramp) to 11 days (platform deployment).

When three signals fire: reply rates below 1% for two consecutive quarters, agency cost per qualified meeting above €2,500, and an internal team capable of running an AI GTM platform with 20% of one FTE's time. Below those thresholds the agency may still be the right answer; above them, the migration pays back within 18 months.

Weeks 1–2: data and CRM audit. Weeks 3–6: signal sources migrated and enriched. Weeks 7–10: workflows rebuilt on the platform. Weeks 11–12: agency contract exit and internal handover. By month 4, the platform is responsible for the full outbound motion under internal supervision.