The Challenge
Insight Action was designed to turn fragmented B2B software evidence into a structured buying-signal system. The hard part was not publishing another software directory. Vendor research, customer source records, renewal pressure, alternatives, comparisons and scoring all had to stay connected so the same underlying evidence could support multiple page types without being rewritten by hand.
A manual workflow would have created duplicated research, inconsistent fields and pages that drifted apart whenever the underlying data changed. The platform needed one repeatable data model, a controlled publishing process and a way to refresh the intelligence on future runs without rebuilding the site.
What We Built
We built the WordPress side around structured vendor data rather than free-form pages. Vendor records, scoring inputs and supporting fields feed reusable templates for the Buying Signal Index, vendor profiles, renewal pages, alternatives and comparisons. That lets the public site present the same evidence through different decision lenses while keeping the source data centralized.
Make handles the orchestration. Structured inputs enter the workflow, AI extracts and normalizes the required information, and the resulting JSON is validated before it reaches WordPress. Custom upsert logic creates or updates the correct records instead of generating duplicates, while taxonomy, SEO fields and template data are mapped as part of the same run.
The workflows were separated by purpose rather than forcing every page type through one oversized scenario. Vendor data forms the base layer; renewal, alternatives and comparison workflows can then consume that structured data and generate the next layer of decision-support content. Status fields and QA gates make it possible to stop a record before publishing when required data is missing or the output needs review.
On the front end, the automation feeds a searchable market index with vendor and category views, evidence-weighted scoring and dedicated pages for different buying questions. The result is a site where the data system and the publishing system are the same architecture rather than two separate products.
Built for Repeatable Market Runs
The important part of the build is what happens after launch. Insight Action is designed around recurring data refreshes, so the workflow can process a new run, update the underlying vendor intelligence and keep the dependent pages aligned without manually editing each one.
That changes the operating model completely: the recurring work is gathering and reviewing better evidence, while WordPress, Make and the structured publishing layer handle the repetitive transformation and distribution underneath it.
