Describe the feature. Claude Code ships it
You own the source, so an AI agent can work on it directly. Point Anthropic's Claude Code at your repo, say what you want in plain English, and read the diff.
An AI developer that works in your repo
Claude Code is Anthropic's coding agent. It runs in your terminal against source code on your own machine, reads the files that matter before it edits, and can run the build and the migrations as it goes.
A rented CRM cannot do this. On a subscription platform the codebase is the vendor's, and there are no files for an agent to open. Ownership is what makes this possible.
$ claude
> Add a proposals module linked to contacts, with a status
dropdown and a PDF export.
● Reading modules/customers.php, app/core/TCustomer.php …
● Found the module pattern — pb_on_action() + PBDBObject
● Writing modules/proposals.php
● Writing themes/tailwind/proposals/list.tpl
● Writing migrations/20260821_proposals.sql
● Running the build … passed
5 files changed, 412 insertions(+)
Review the diff with: git diffA codebase built to be read by an agent
Agents do well on consistent code and badly on clever code. This platform was written, and is extended by us in production, with exactly that in mind.
Conventions an agent can follow
One query pattern, one module pattern, one template structure, used across the whole platform. An agent that reads three modules can write the fourth.
Docs written to be executed
The install and architecture docs are instructions for an agent, not prose to translate. Point it at the folder and it can follow them end to end.
A gotchas file
The traps that catch new developers are written down where the agent will read them: the helpers that exist, the tenant scope every query needs.
Live schema, not a stale diagram
The Schema Explorer reads the running database, so the table and column names handed to the agent are the ones that exist today.
From idea to deployed, in five steps
The same loop we use to extend the platform ourselves.
- 01
Describe the feature
Open the AI Developer panel and type what you want in one paragraph. No file paths, no boilerplate.
- 02
It assembles the context
The panel attaches the live schema, the conventions, the module patterns and the gotchas, so the agent does not have to guess.
- 03
Paste it into Claude Code
You get a complete build prompt. Paste it into the terminal and let the agent work.
- 04
Review the diff
The agent edits files in your working tree. Read the diff like a pull request and keep or discard it with git.
- 05
Ship it
Run the migration, commit and deploy with the rebuild script the platform ships with.
What people actually type
On a rented CRM these are roadmap conversations. Here they are an afternoon.
“Build an appointments module linked to contacts with a date picker and a status dropdown.”
New module with full CRUD and a pipeline tab, the migration included, and a mobile-ready template.
“Add Google Calendar sync to the appointments module.”
OAuth flow, a cron job, two-way sync and a settings panel, wired into the existing module.
“The contact form submits without an error but nothing saves to the database.”
Root cause, the exact file and line, and the fix, checked against your actual schema.
“Show a pipeline forecast on the dashboard: deals by stage with expected close dates.”
A dashboard widget using the chart library already in the repo, reading the real tables.
What you need to run it
Four things, three of which arrive with the platform. The build prompt is plain text, so Cursor, Windsurf or any agent that can read a repo works too.
Your copy of the source
Handed over at purchase as a private repository. Claude Code works on files on your machine.
A Claude account
Claude Code is Anthropic's product, billed by Anthropic on your own subscription or API credits. Nothing is resold or marked up here.
A terminal and git
If you can clone a repo and run a command, you have everything you need.
The local Docker stack
The included compose file runs the whole platform locally, so changes can be tried before they reach a customer.
You stay in control of every change
An agent editing your codebase should feel like a developer handing you a pull request, not a black box redecorating production.
- Every change lands in your working tree. You read the diff before anything is committed.
- Git is the undo button. Discard a change you do not like and nothing is lost.
- Try it on the local Docker stack before it touches production.
- Migrations are timestamped files, so a schema change is reviewable like any other code.
- 30-day code warranty on the platform you bought, whatever you build on top of it.
Own the entire acquisition engine — source code and all
One price, no per-seat fees, no monthly rent on your own pipeline. Host it yourself, or let us host it for $199/mo. A 30-day code warranty backs the delivered source.
$5,000
One Time Payment
Own It Forever
- Full source code — web + mobile
- 145M-contact B2B database
- AI agents + automated outreach
- Full CRM + built-in AI Developer