Our role
Designed and developed for the client: relationship data model and the Gmail, Calendar, Stripe and Segment integrations.
What it is
Relationship CRM
Industry
Professional services
Live at
nat.app
Public traction
About $12K/month in reported revenue
Indie Hackers, as of September 2026
A personal CRM that reads your email and calendar to keep relationships warm: reminders, notes and pipelines built from the conversations you already have, with Stripe and Segment data alongside.
The problem
Relationships live in an inbox and a calendar, and both are poor at mentioning that a good contact has gone quiet. A conventional CRM answers this by asking a person to type what already happened into a second system, which is why the CRM is abandoned almost as soon as it is set up.
The first call
The first call ruled out data entry. A record that has to be typed will not exist, so the build had to read what was already happening: mail, meetings, and the commercial signals sitting in Stripe and Segment. What the user adds is judgement, not history.
What we built
A relationship CRM assembled from Gmail and Calendar, with Stripe and Segment data alongside, so a contact carries its own conversation, meeting and revenue history without anyone maintaining it. Reminders and pipelines sit on top of that record instead of on a form somebody has to fill in.
How they run today
The CRM fills itself. A user opens it to see who has gone quiet, what was said last time and what the relationship is worth, then writes a note — the only typing the product asks for.
What changed
Keeping in touch became a habit rather than an administrative project. The relationships that quietly lapse are the ones this catches, and those are the expensive ones.
Screens
Services behind it
- Custom SaaS DevelopmentSubscription products and business platforms, from architecture to deployment.Multi-tenant architecture, Billing, Admin panels, Onboarding
- Legacy Software + AI ModernizationModernize what you have and add AI without a risky rebuild.Backend modernization, API layer, Database modernization, Cloud migration
Not sure where to start?
Describe the problem in a few lines. You get a straight answer on what we would build and how long it takes.