A
The sealed vendor
Every request joins a queue for the yearly release. You can't see inside, so nobody can say why a rule fired.
CRM as code
Write the companies, people, deals and stages your team sells with as code. Review each change in a pull request and ship it with the rest of your product.
Free while your team has five seats or fewer.
Used by engineers at payroll, robotics, travel, insurance and developer tool startups.
Where CRM changes get stuck
A
Every request joins a queue for the yearly release. You can't see inside, so nobody can say why a rule fired.
B
The first version goes out in a month. Then each change breaks something, and each fix takes longer than the last.
A third way
Objects, fields, stages and rules sit in plain files next to your app.
A payroll startup moved its deal stages into the repo. Sales asks in an issue, an engineer opens a pull request, and the head of sales approves it.
Engineering lead, payroll startup
A robotics leasing company runs every pipeline change on a laptop against last month's records before it goes live.
Platform engineer, robotics leasing
A travel booking startup ships CRM changes in the same deploy as product changes, so there is one schedule to plan around, not two.
CTO, travel booking startup
How it works
01
A data model, a layout and an automation. Put them together for your CRM, or for a small internal app such as deal approvals.
02
Tell your coding tool you need a renewals stage. It edits the model, runs the tests and deploys. The board gets a new column, and the next won deal can start a renewal.
03
Save a file and the CRM on localhost reloads with real rows from your local database. The tests run as you save, so you know before you push.
For your sales team
Four stages, deal cards and a running total over each column. Drag a deal and the totals follow it.
Accept a suggested edit on a deal and the table, the board and the chart change together.
Press Cmd K, type three letters, and the list narrows to the action you want.
Customer stories
2 daysFrom request to live stage
Payroll startup
A renewals stage went from a chat message to production in one review.
41Reviewed model changes this year
Robotics leasing
Each new field and rule has an author, a reviewer and a passing test run in the history.
1Deploy for product and CRM
Travel booking
Booking features and the sales pipeline go out together, so neither team holds up the other.
Sales stopped filing tickets
Our head of sales opens issues in our repo now. Most of them are merged by Thursday, and she reviews the preview herself.
I can read the history
A deal jumped stages and nobody knew why. I found the commit in a minute. With our old vendor that was a support call and a week of waiting.
Same tests, same deploy
We already had CI. Now the pipeline rules go through it like everything else, and sales gets new stages on our normal Tuesday release.
Questions
Want to see a model file first? Book a call and we'll walk through one with you.
In your repository, as typed files. Objects, fields, relations, stages and rules are all code your team can read and review.
Yes. Views, filters and saved lists are set in the app. Anything that changes the model goes through a pull request.
Run Corvane on your laptop against a local database seeded with real records. The tests run each time you save.
With your normal deploy. Corvane reads the model from your build, so the CRM and the app go out together.
Yes. The model is plain code with types, so the coding tool your team already uses can edit it and run the tests.
Export a CSV and run the import script. Map its columns to your objects in code and try it locally first.
Free for up to five seats. From the sixth seat on, you pay monthly for each one.
Clone the starter repo, run it on your laptop and open your first pull request today.