Growth Engine
B2B growth engine system entry
This section is separated from the minimal blog: it is the operating surface for verified lead discovery, content matrix automation, risk checks, CRM sync, publishing, analytics, and daily reports.
Current status: WordPress migration files are prepared locally. Live WordPress operation still needs hosting/admin access, API credentials, and domain routing.
Migration status
Operating flow
-
Product, country, buyer type, claims, and APIs
The system reads the product configuration, approved claims, target markets, CRM rules, publishing channels, and report settings before any automation runs.
-
Discovery, verification, scoring, and CRM save
Leads must pass the three-evidence rule: company identity, product relevance, and contact path. Qualified A/B leads receive outreach drafts but are not auto-sent.
-
One core topic becomes platform-specific content
The engine creates LinkedIn, Facebook, Instagram, YouTube Shorts, TikTok, and Blog outputs from the same approved product knowledge base.
-
Low-risk content can publish; high-risk claims wait
Price, delivery, certification, legal, named-customer, competitor, and guaranteed-performance claims are held for review unless already approved.
-
Metrics improve lead scoring and topic selection
Post performance, website clicks, inquiries, replies, and CRM status changes feed back into future query weights, topic scores, and outreach angles.
WordPress migration package
Prepared files include a Supercaly WordPress theme, a Growth Console plugin, a WordPress import XML file, and setup documentation. After WordPress hosting is available, the migration path is: install theme, install plugin, import XML, set the Growth Engine API URL and bearer token, then route the domain to the WordPress host.
The public site can keep the blog minimal while the engine runs as a protected project section. Customer registration, Facebook connection, monitoring, publishing feedback, and reports should live behind authenticated WordPress pages or a connected app dashboard.
A same-domain console is now available at /growth-engine/console/. On Vercel it expects server-side environment variables for the Growth Engine API base, API token, and optional console token.
Automation boundary
The system can automate discovery, verification, scoring, content creation, approved scheduling, publishing, CRM updates, analytics, and reporting.
It must not automate unsolicited DMs, comments, likes, follows, fake account behavior, CAPTCHA bypassing, login-required scraping, unsupported claims, or unnecessary personal data collection.