Drupal Commerce
Public commerce capabilities and supporting storefront technologies.
Drupal intelligence
Know which Drupal estates are worth a closer look now.
Kaiju watches public Drupal estates for architecture changes, hiring, platform signals, and other evidence your specialists care about. See fit, signals, people, and proof in one account view.
Example sales brief
ICP
- Complex Drupal estates
- North America
- Enterprise and public sector
Services
- Modernization
- Migration
- Architecture
Evidence
- Drupal Commerce
- Multisite
- Headless
- Search and infrastructure
Watch for
- Platform migration
- Frontend change
- Digital-team expansion
One estate
See why this estate deserves a closer look.
Example account
Civic North
civicnorth.example
- Fit
- Strong Drupal fit
- CMS
- Drupal
- Architecture
- Headless clues
- Search
- Solr
- Edge
- Cloudflare
- Frontend
- React
- Estate
- Multiple properties
Estate and company context match the selected service ICP.
A supported technology fact, with public application evidence attached.
Frontend and API evidence merits specialist review; presence alone is not a dated signal.
Public search integration detected.
CDN and security context around the site.
Decoupled application clue.
Public links and patterns suggest a broader estate.
The estate
See the estate conditions your specialists care about.
Multisite
Public clues that point to a larger multi-site or multi-property estate.
Headless architecture
Decoupled frontend, application, and API clues visible from the public site.
Search
Search platforms, services, and integrations exposed by the website.
CDN and security
Edge, CDN, WAF, security, and delivery technologies around the site.
Frontend architecture
Themes, components, JavaScript, CSS frameworks, and application layers.
Analytics
Analytics, marketing, consent, and measurement services.
Public modules and themes
Modules, distributions, themes, and services only when they leave public evidence.
The work
Connect those conditions to the work you sell.
- 01
Modernization
Use frontend and architecture conditions as account context. Track supported changes separately when timing matters.
- 02
Migration
Use estate evidence to qualify a migration hypothesis; require dated change evidence before calling it a Trigger.
- 03
Replatforming
See the public systems and dependencies around the estate.
- 04
Support
Map the visible Drupal and infrastructure context before a support conversation.
- 05
Performance
Bring public performance evidence into account review.
- 06
Architecture
Combine estate conditions, dated changes, people context, and source evidence in one account view.
Pricing
Choose your plan.
Starter
From what you know to a usable List
For founders and independent sellers who want Kaiju to help turn a business, specialty, or initial account set into a focused prospecting workflow.
$247.50/ month
Monthly rate $275/mo
Save 10% · billed annually
- Evidence-backed account intelligence
- Editable targeting and Lists
- CSV import & export
Partner Program eligible
Choose StarterGrowth
Connect Kaiju to your GTM stack
For small GTM teams that want Kaiju connected to the systems where prospecting work already happens.
$427.50/ month
Monthly rate $475/mo
Save 10% · billed annually
- Everything in Starter
- Released CRM & workflow integrations
- Webhooks and automated delivery
Partner Program eligible
Choose GrowthTeam
Shared GTM infrastructure
For teams coordinating multiple GTM motions across a shared workspace.
$877.50/ month
Monthly rate $975/mo
Save 10% · billed annually
- Everything in Growth
- Shared workflows and advanced routing
- API access and higher research limits
Partner Program eligible
Choose TeamSee full plan comparison
Full plan comparison
Know exactly what each plan includes.
The cards above are the short version. Use this table to compare sales intelligence, account workflows, allowances, and connected-delivery features across Starter, Growth, and Team.
| Feature | Starter | Growth | Team |
|---|---|---|---|
| Sales intelligence | |||
| Evidence-backed account intelligenceResearch company, people, technology, website, and other supported evidence across an account list, with sources kept available for review. | Included | Included | Included |
| Public evidence attached to findings | Included | Included | Included |
| Original CSV fields and IDs preserved | Included | Included | Included |
| Incomplete and ambiguous result states | Included | Included | Included |
| CSV import & export | Included | Included | Included |
| Lists and qualification | |||
| Lists | 3 | 6 | 12 |
| Criteria per list | 3 | 6 | 12 |
| Targeting, filtering, and priority workflowFilter supported findings, narrow the List, and review why an account is prioritized before moving it forward. | Included | Included | Included |
| Connected workflows | |||
| Released CRM & workflow integrationsConnector availability follows each integration's published status. Twenty is the current CRM priority and remains in development. | Not included | Included | Included |
| Webhooks | Not included | Included | Included |
| Automated delivery | Not included | Included | Included |
| Shared team workflows | Not included | Not included | Included |
| Advanced routing | Not included | Not included | Included |
| API access | Not included | Not included | Included |
| Research limits | Standard | Higher | Higher |
Annual Partner Program
Make Kaiju fit the workflow you already run.
Annual customers can work closely with Kaiju to scope, build, and refine the integration between Kaiju and the sales, CRM, research, or operations workflow they already use. The Partner Program is not a fourth plan or an unlimited services bundle. It is hands-on integration work around the annual plan you choose.
Map the existing workflowBuild the agreed integrationRefine it with your team
Introductory Kaiju access
Available before billed usage
Open an introductory workspace before billed usage. Campaign and CTA identity can select the introductory allowance and setup policy. Billing begins only after a plan choice or explicit confirmation of the applicable commercial terms.
Drupal research questions
Know the limits of public Drupal research.
Can Kaiju identify exact Drupal versions?
Sometimes. Kaiju reports an exact version only when the public evidence supports it.
Is Drupal presence a signal?
Usually no. Technology presence is a fact that can support ICP fit. A dated migration, estate change, hiring acceleration, or another supported event can satisfy a Trigger definition when timing carries sales meaning.
Can Kaiju see every installed module?
No. Kaiju can report modules, distributions, themes, and services that expose public evidence. It cannot prove the complete private Composer or administration state.
What happens when the evidence is unclear?
The result stays incomplete, contradictory, or unknown. A missing value is not treated as a confident no.
Can I start with our existing account list?
Yes. Keep the domains, IDs, owners, and other source fields your team already uses.
Drupal intelligence
Put your Drupal expertise across the market.
Start with estates your specialists know. See which ones fit, what changed, and where the evidence supports a conversation.