Pilots & Pricing
Start with the smallest useful public-record workflow.
Akil engagements usually begin with a focused pilot: one address workflow, one organization workflow, one district workflow, or one developer integration. From there, the scope expands only if the record layer proves useful.
Pilot Models
Common ways to start.
Workflow pilot
Turn one recurring public-record question into a repeatable source-backed workflow, usually around a property, organization, district, agency, or funding question.
Developer pilot
Connect a product, dashboard, agent, or internal tool to Akil's MCP-accessible public-record layer for a bounded set of sources and use cases.
Partner pilot
Package Akil's public-record layer into a partner service, report, client workflow, or white-labeled product for a defined audience.
Scope Drivers
What affects pricing.
Record families
Property, permits, violations, ACRIS, zoning, licenses, procurement, grants, lobbying, campaign finance, legislation, and neighborhood conditions each have different complexity.
Output form
A lightweight report, analyst workflow, embedded dashboard, MCP integration, and white-labeled product require different implementation depth.
Trust requirements
High-stakes diligence may require stronger coverage disclosure, audit notes, fixtures, human review gates, or source-specific methodology.
Operational support
Some partners only need the data layer. Others need workflow design, training, change management, or ongoing implementation support.
First Conversation
Bring one concrete workflow.
The fastest path is not a broad platform evaluation. It is one question your team already answers manually, one user group that needs it, and one output that would make the work easier.