Methodology
The method behind the platform.
Ancil is not a blank canvas. It ships with a point of view, refined across 1,500+ HubSpot deployments at INSIDEA. Here is what we believe, and how it shows up in the product.
P01
Data foundation
Every HubSpot engagement starts with the object model. Get properties, lifecycle stages, and deal pipelines right before you build anything on top.
- One source of truth per concept
- Lifecycle stage before campaigns
- Required fields gate pipeline advancement
- No duplicate properties across objects
P02
Operational rigor
Workflows, lists, and integrations must be explainable, exit-able, and reviewable. No black boxes. No orphaned assets.
- Every workflow has explicit exit criteria
- Static lists are time-stamped or deprecated
- Integrations have owners and kill switches
- Automation documented inside HubSpot, not outside
P03
Revenue visibility
Reports should answer one question. Dashboards should answer three. No dashboard should answer ten. Clarity over comprehensiveness.
- Forecast dashboard is sacred
- Attribution models are chosen, not accumulated
- Pipeline reviews use one shared view
- Revenue ops owns the reporting layer
P04
Team fluency
A HubSpot portal is as healthy as the least-trained person using it. Training is part of implementation, not an afterthought.
- Training is role-based, not feature-based
- Short videos, long cheat sheets
- Onboarding new hires is a repeating flow
- A named HubSpot owner exists forever