TWENTY CRM ROLLOUT AND BUSINESS CHECKLIST
Ken Designers · kendesigners.com/articles/twenty-open-source-crm-business-kenya/
Planning aid only. Not legal advice. Check current Twenty terms and prices.

---------------------------------------------------------------
1. MAP THE SALES PROCESS (before touching software)
---------------------------------------------------------------
Where leads come from: [ ] WhatsApp [ ] calls [ ] website [ ] walk-ins [ ] referrals [ ] ______
Pipeline stages (5-7):
 1. ________  2. ________  3. ________  4. ________  5. ________  6. ________
Required fields (keep to 5): name / phone / source / value / ________
Custom objects needed (e.g. plots, applicants, outlets): ________________
CRM owner (one person): ________________

---------------------------------------------------------------
2. CLOUD OR SELF-HOSTED?
---------------------------------------------------------------
Users: ____ x $9 (Pro, yearly) = $____/month   or   $19 (Organization)
Need SSO / row-level permissions / custom domain? [ ] yes -> Organization
Self-host: server ($12-$24) + backups ($__) + someone's time
Decision: [ ] Cloud  [ ] Self-host  [ ] Managed by a provider

---------------------------------------------------------------
3. SELF-HOSTING SET-UP
---------------------------------------------------------------
[ ] Ubuntu server, Docker, >= 2 GB RAM
[ ] ENCRYPTION_KEY generated AND stored in a password manager
[ ] PG_DATABASE_PASSWORD without special characters
[ ] SERVER_URL=https://crm.______.co.ke
[ ] HTTPS via Caddy/Nginx
[ ] Nightly pg_dump backup copied off the server; restore tested
[ ] Version pinned; upgrade = backup -> test copy -> upgrade

---------------------------------------------------------------
4. FIRST WEEK CONFIGURATION
---------------------------------------------------------------
[ ] Pipeline and stages created
[ ] Contacts and open deals imported from Excel (CSV)
[ ] Workflow: quote sent -> call-back task next day
[ ] Workflow: weekly stale-deal reminder to owners
[ ] Email and calendar connected for the sales team
[ ] Dashboard: deals by stage, won this month, lead source

---------------------------------------------------------------
5. LOCAL CONNECTIONS
---------------------------------------------------------------
[ ] M-Pesa: Daraja callback -> Twenty webhook workflow (find by phone,
    mark paid, record receipt)
[ ] WhatsApp: new enquiry -> create/update person in Twenty
[ ] Invoicing / KRA eTIMS stays in accounting tool; invoice ref on deal

---------------------------------------------------------------
6. ADOPTION RULES
---------------------------------------------------------------
[ ] "If it's not in the CRM, it doesn't count" agreed
[ ] 15-minute Monday pipeline review scheduled
[ ] Staff trained (30 minutes each), short how-to video recorded

---------------------------------------------------------------
7. IF YOU SELL SERVICES OR A SAAS
---------------------------------------------------------------
[ ] Own brand; described as "built on Twenty"; no Twenty logo as mine
[ ] Value kept in apps using published APIs/SDK (Application Exception)
[ ] Any core modifications offered as source to users (AGPL)
[ ] No enterprise-licensed features in production without subscription
    (SSO, row-level permissions, custom domains, event logs, billing)
[ ] Own billing (e.g. M-Pesa via Paystack, 1.5%)
[ ] One instance per client, or multi-workspace licence checked
[ ] Provisioning scripted; support hours priced in

Notes: