Instead of Rocketlane
Stop renting Rocketlane. Own your customer onboarding system.
We build your version around how your team gets customers started, bring your Rocketlane records across and run it for you. Your milestones, your acceptance rules and a clear handover.
Rocketlane lists Standard at US$49 and Premium at US$69 per team member per month, billed annually, with a five-person minimum.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription buys
Your delivery process sits inside a seat-based service
Rocketlane combines customer collaboration, project delivery and reporting. Compare what your team uses with the onboarding system you want to own.
A licence for each team member
Standard is US$49 per team member per month on annual billing.
A higher tier for more management features
Premium is US$69 per team member per month on annual billing.
A minimum team commitment
Both published plans require at least five team members.
A shared customer space
The subscription includes a customer portal and unlimited customer members.
Reporting alongside the plan
Project reporting is included, with custom reports listed in Enterprise.
Implementation outside the licence
Rocketlane prices implementation packages separately according to scope.
Your owned version
Make the handover depend on evidence
Customer commitments
Know whose work is holding up delivery
Customer responsibilities stay attached to the implementation they affect.
- check Name an owner and date for each task
- check Separate customer work from internal work
- check See overdue customer commitments together
- check Draft a status note from the current plan
Dependencies
Find the work that cannot start yet
Review prerequisites before telling a customer the next step is ready.
- check Keep linked work within its own project
- check Reject circular dependencies
- check Require prerequisites before recording completion
- check Reopen dependent work before reopening its completed prerequisite
Acceptance
A finished task is only part of the handover
Customer acceptance and launch approval are separate records with their own evidence.
- check Require completed work before milestone acceptance
- check Record who accepted the milestone and why
- check Clear acceptance when its task list changes
- check Check every milestone before recording launch
Weekly review
Use your own definition of a healthy implementation
Read current delivery, effort and privacy checks together, then change the rules as your business changes.
- check Find projects with no recent update
- check Compare logged hours with the project budget
- check Prepare branded kickoff and handover documents
- check Review missing privacy evidence and review dates
Make it yours
Design your own Rocketlane replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Rocketlane. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Rocketlane data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Customer Onboarding for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Customer Onboarding for Claude Code
Connected to your own database
Which customer tasks are holding us up?
Kauri migration
- Milestone
- Acceptance
- Name
- Approve migration rehearsal
- Owner
- Leo
- Responsible
- customer
- Status
- waiting
- Due_on
- 2026-10-07
- Effort_hours
- 3
- Overdue
- true
- Blockers
- 0
Harbour rollout
- Milestone
- Data ready
- Name
- Supply customer records
- Owner
- Mira
- Responsible
- customer
- Status
- waiting
- Due_on
- 2026-10-08
- Effort_hours
- 2
- Overdue
- true
- Blockers
- 0
| Project | Milestone | Name | Owner | Responsible | Status | Due_on | Effort_hours | Overdue | Blockers |
|---|---|---|---|---|---|---|---|---|---|
| Kauri migration | Acceptance | Approve migration rehearsal | Leo | customer | waiting | 2026-10-07 | 3 | true | 0 |
| Harbour rollout | Data ready | Supply customer records | Mira | customer | waiting | 2026-10-08 | 2 | true | 0 |
Ask it anything
Ten questions for your delivery meeting
These answers come from the working demo below. Rocketlane also offers reporting. The difference here is that you own the records and can change the rules behind each answer.
Switching
How to switch from Rocketlane
A move usually involves exporting your project and task records, checking the import, and reconciling the history and rules you choose to bring across.
- 1
Export projects and tasks
Export your Rocketlane project list and task list as CSV. Check the headings and dates before you use them. Make a separate list of the history you need to reconcile, such as attachments, comments, dependencies and approval history, since these are not brought across by the project and task import. Keep your Rocketlane account available while you check the new records.
- 2
Test the import
Run a test import without saving records first. The importer checks the project and task data, keeps the original source fields and validates names and dates. Review the test results, correct heading or date issues, and normalise any custom statuses before you load the records. The import can use mapped headings when your export labels differ from the expected ones.
- 3
Review flagged records
Check every validation finding and resolve errors before relying on the imported plan. Changed source rows need reconciliation, and custom statuses must be normalised. Imported completed tasks are recorded as source-reported completion, not customer approval. Milestone acceptance still needs a reviewer and evidence. Reconcile dependencies, customer sign-offs, files, comments, financial records and portal accounts separately if you need them.
- 4
Run both systems briefly
Keep Rocketlane and the new database in use side by side for a short period while your team checks the active projects, tasks, owners, dates and customer waits. Confirm that the records match your operating process and that acceptance evidence is present where required. Use this check to resolve gaps before you make the new system the place your team maintains current work.
- 5
Switch off Rocketlane
Once your team has checked the active work and resolved the migration issues, stop maintaining those records in Rocketlane and use the new system as the working record. Keep any history or evidence files you still need, and make sure you have a separate backup of the database and evidence files. Do not treat imported task completion alone as customer acceptance.
Where the real effort goes
The import itself is only part of the work. Most effort usually goes into mapping your own fields and statuses, deciding which history to bring, and reconciling items the project and task import does not cover. If you have Enterprise DNA run it, they handle this migration work as part of the setup, including your fields, rules and agreed records.
Not ready for a call?
Get your Rocketlane switch plan by email
We will send you the step-by-step plan for moving your business off Rocketlane, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Rocketlane switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to run it
Choose how much you want us to handle
Open source
Do it yourself
Free, open source
- 1 Clone the repo and install its dependencies
- 2 Run npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
- 3 Ask for /weekly-review and inspect the fictional projects
- 4 Prepare the Rocketlane project and task CSV exports, then test the import
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your delivery stages, fields and acceptance rules
- check Your Rocketlane exports mapped and reconciled
- check A customer website and notifications if you want them
- check Your preferred technology and business connections
Omni by Enterprise DNA
We run it for you
One setup fee, then a monthly retainer
- check Installed and operated through Omni by Enterprise DNA
- check Your customer records brought across and checked
- check Access, backups and operating responsibilities agreed with you
- check Your system maintained as your delivery process changes
Questions
Instead of Rocketlane, answered
What exactly does the free version replace? expand_more
It provides the working onboarding register: customers, projects, milestones, tasks, dependencies, updates and acceptance evidence. The comparison is about owning that process. We scope the rest of your Rocketlane workflows into your custom version.
Can we bring our existing Rocketlane projects across? expand_more
Yes. Export the project list and task list as CSV, check the headings and dates, then do a test run. The free importer preserves the source fields and checks each record. We reconcile attachments, comments, dependencies and approval history separately as part of your migration.
Does an imported completed task count as customer approval? expand_more
No. Completion from the export is recorded as source-reported completion. Milestone acceptance still needs the reviewer and their evidence. Launch remains blocked until the work and acceptance checks pass.
Can customers have their own place to check progress? expand_more
Yes. Enterprise DNA builds customer access, notifications and connections into your version when those are part of the agreed scope. We agree who can see and change each record before it goes into use.
What do we pay Enterprise DNA? expand_more
One setup fee, then a retainer for the ongoing work you agree with us. We start with your process, your Rocketlane export and the access your team needs. The free version has no licence fee. Hosting and the service used to operate it have their own costs.
Build the onboarding process you want to keep
Spend 30 minutes with Sam. Bring your Rocketlane bill and one implementation that keeps getting stuck. We look at the work, the customer handover and what your own version needs to do.
Customer Onboarding for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Rocketlane?
Get your version built