Configure a CRM
Fast when your process fits. Use one when you need a hosted product now.
The open-source custom CRM framework for coding agents
Your business is different.
Your CRM should be too.
Tell your coding agent how you sell and serve customers. Accordo gives it the rules. You keep the code.
- Lead
- Qualification
- Opportunity
- Quote
- Approval
- Order
- Contract
- Renewal
policy gate · discount > 20%
- Agent request−25%The agent proposes the discount through a named workflow
- Policy checkBlockedAbove the threshold the transition refuses itself
- Human decisionApprovedA named person decides; the agent cannot decide for them
- Audit recordedFlow resumesThe decision leaves a trace in your repository
Custom CRMQuote approvalRevenue opsServiceRenewalsCPQCustomer data
In practice
Describe the rule. Your agent ships it. Your team uses it.
One sentence of business intent becomes a versioned policy in your repository — and the CRM screen your team opens obeys it.
Business intent
“When a quote has more than 20% discount, a sales manager must approve it.”
$ npm run crm -- app inspect --json→ composition read, not guessed→ plan bound to this application
Source · commercial/discount-policy.js
export const standardSalesDiscount = {
name: 'standard-sales-discount', version: 1,
config: { autoApproveMaxBps: 2000, ●
approvalKey: 'sales-manager' }, ●
evaluate({ maxLineDiscountBps, config }) {
if (maxLineDiscountBps <= config.autoApproveMaxBps)
return { decision: 'auto_approve' };
return { decision: 'approval_required', ●
requiredApprovalKey: config.approvalKey };
},
};
Matching marks — the line of policy that governs the behavior.
The backend enforces it
One application — UI, domain model, services, workflows, policy and audit — composed as source in your repository. The client asks; the server decides.
accord reached · sealed
A third choice
Stop choosing between bending a platform and rebuilding CRM foundations.
Build with Accordo
Start from CRM primitives. Let the agent shape them around your process, in a repository you control.
Generate from scratch
Maximum freedom, but your team must re-derive policy, audit and verification.
The signature moment
A rep wants to give 25% off. Who gets to say yes?
✓ Every decision leaves a trace — audit and run history stay in your repository.
One operating model
From first signal to the next customer decision.
Model the lifecycle as connected business outcomes—not a collection of disconnected objects.
- Customer context
- Demand
- Qualification
- Opportunity
- Quote & approval
- Signature & order
- Contract
- Delivery
- Service
- Renewal
Agent-native developmentWorkflow & policyHuman approvalAudit & trace
Product model, not a coverage claim. The lifecycle is the durable system Accordo is designed to express. Repository evidence separately shows which parts this exact tree proves.
Why it is different
Business rules become reviewable software.
Process before schema
Start with the job, decisions and boundaries. The data model follows the way the business works.
Agents author; policy decides
Commercial policy is deterministic code, not a model's judgement: a renewal at or above the threshold stops and waits for a named human.
See the proof and its boundaryHuman decisions stay human
Authority is a property of the system, asserted by a test — not a promise in a README.
See the refusal proofSource ownership is literal
The scaffolder vendors framework source into your project. Upgrades are merges, not dependency bumps.
Understand the ownership mechanismThe coding-agent experience
Intent in. Checked-in system out.
- DescribeState the business objective, constraints and decisions.
- InspectThe agent reads the composition instead of guessing what exists.
- PlanIt binds a reviewable plan to that exact application.
- BuildIt composes packages, workflows, policy and UI as owned source.
- ProveTests, scenarios, audit and trace show what worked—and what was not established.
Jobs, grouped for humans
Build around the commercial job in front of you.
Custom CRM designEncode a non-standard sales process without forcing it into somebody else’s object model.Revenue operationsConnect lead, opportunity, pricing, approval, order and the work after sale.Quote & approvalTurn commercial rules into deterministic pricing, versioned policy and human gates.Delivery & serviceCarry customer context into delivery obligations, support and the next commercial decision.
Desired jobs are not implementation claims. Each solution page separates the job and target workflow from the capabilities and evidence currently available.
Product proof
Claims travel with their tests.
Every sentence on this page resolves against a ledger bound to the test suite. Follow any claim to the test that proves it — and to the boundary that travels with it.
C-03Commercial policy is deterministic code, not a model's judgement: a renewal at or above the threshold stops and waits for a named human.✓ workflow evidence
C-14One command tells an agent what an application actually is — packages, capabilities, resources, actions, policies, providers — read from checked-in source, in a single deterministic JSON report.✓ app-inspect evidence
C-17SQLite is Node's built-in node:sqlite. PostgreSQL requires one pinned runtime driver, pg@8.23.0. There is no ORM, no query builder, no build step and no framework underneath your framework.✓ no build step
sealed · measured at bffb1c2 · 2026-09-19 · 2196 tests, 0 failing
Open source. Self-host framework source. Deployments require an application-supplied authentication verifier and operational configuration. Passing tests does not certify production readiness.