PocketOps for Twenty

Twenty is an open source CRM you can run on your own server. I run several of them: my own business CRM, plus one for each customer I build for. The gap was always the phone. There was no good mobile client for self-hosted Twenty, so I built one, and in August 2026 it shipped to the App Store and Google Play.

PocketOps connects directly to your Twenty instance. Your server, your API key, no middleman, and no data collection. Nothing about your business passes through anything I own.

Work your day from a phone

The Today screen pulls the day together: appointments, tasks due and overdue, pipeline moves, and money collected, with a morning brief written from the actual state of the CRM. Below that it is a full client: browse and search people, companies, and deals with server-side search that stays fast on thousands of records, create and edit records, and fire the workflows the workspace already has, like sending a welcome email from a client’s record with one tap.

It adapts to any workspace, not just mine

This was the hard part and the point. Twenty lets every business define its own objects, fields, and views. A tattoo studio has procedures and artists; a consultancy has projects and invoices. PocketOps does not hardcode any of that. It reads the workspace’s own schema at connect time, discovers custom objects and relations, mirrors saved views as filter chips, and builds its create and edit forms from what the server says it will accept. Point it at a different Twenty and you get a different app.

AI with a leash

There is a chat tab where you can ask the CRM questions in plain language: what’s overdue, what moved in the pipeline, prep me for this meeting. Anything that would change data stops first at an approval card showing exactly what it is about to do. Reading is free, writing asks permission.

The other half: I build the CRM too

The app is one end of a service. On the other end I set up the whole system for small businesses: a Twenty instance on its own server, the schema shaped to how the business actually works, automated workflows for things like welcome and aftercare emails, Square payments syncing in every half hour, the website booking form writing straight into the CRM, and separate dashboards for the owner and the staff. The first production deployment runs a permanent makeup studio: bookings come in from the website, deposits go out through Square checkout links, and aftercare instructions email themselves per service. The owner runs it from her phone with this app.

If you run a small business and want a CRM you actually own, that is exactly the kind of project I take on. Get in touch.

Built without a Mac

A fun one for the builders: this is a React Native app built and shipped to Apple’s App Store entirely from a Windows machine using Expo’s cloud build service. No Mac was involved at any point, including the screenshots.