Selected Work - Automation

SentiKits - a trial-to-paid funnel that runs without anyone watching

Onboarding, entitlements, and the trial-to-paid path are the kind of work that quietly breaks when done by hand-or doesn't happen at all. I automated the lifecycle: a guided first run, a 5-state entitlement model, and server-verified subscriptions that move users from free to paid on their own.

Role

Founding Engineer / Automation

Focus

Onboarding · Entitlements · Funnel

Links

TestFlight (iOS beta)

01The problem, and the manual way it was handled

A trial-to-paid funnel is a sequence of small, time-sensitive decisions: get a new user to their first real moment, track where they are in a trial, grant the right access, verify the purchase, and handle the edges like expiry, refunds, and redeem codes. Done by hand it is slow and impossible to scale, and a missed step either leaks revenue or hands paid features to someone who did not pay. In a wellness app the automation also has to feel invisible, so the work was to make the funnel run itself reliably while staying gentle.

02What I automated

  • Guided onboarding - a spotlight tour that automatically walks a first-time user to their first reflection-no manual hand-holding, no drop-off in setup.

  • 5-state entitlement model - free, trial, and paid states transition automatically as a user moves through the funnel, gating features without anyone flipping a switch.

  • Server-verified subscriptions - purchases are validated server-side through Apple IAP so access is granted-or revoked-by the system, not by trust.

  • Multiple on-ramps - free tier, trial, and physical-kit redeem codes all feed the same automated entitlement path-different users, one funnel.

03Automation decisions

Funnel as a state machine

Problem
Tracking who is in a trial, who converted, and who has access by hand does not scale past the first handful of users.
Approach
I modeled the funnel as a five-state machine with automatic transitions and server-verified entitlements, so progression and access are computed rather than administered.
Result
The funnel onboards, trials, and converts users with no one in the loop and no leaked access.

Automation the user can't feel

Problem
Billing and entitlement logic, if surfaced clumsily, breaks the calm tone the whole product depends on.
Approach
I ran the funnel automation behind the warm, guided experience, the breathing intros and gentle prompts, so the machinery stays out of sight.
Result
The app still feels calm and safe while a conversion engine runs underneath it.

Scheduled entitlement reconcile

Problem
Trials, 12-month redeem codes, and renewals each lapse on their own clock, and left alone, access drifts into stale grants or wrong lockouts.
Approach
I run a daily Cloud Function that expires lapsed trials and codes and re-checks renewals against server-verified receipts, so entitlement state reconciles itself every night.
Result
Access stays correct with no manual audits and no leaked entitlements.

Notification fan-out in triggers

Problem
Live notifications across posts, comments, likes, and messages usually mean standing up and running realtime infrastructure.
Approach
I did the whole fan-out in Firestore triggers writing to a server-only notifications collection that clients can read but never write, so delivery runs server-side with nothing to operate.
Result
Trustworthy, real-time notifications with no realtime infrastructure to run or get paged about.

04How it was built

One React Native codebase on a serverless backend, cheap to run and easy to automate.

React NativeFirebaseCloud FunctionsApple IAPShopify

05Outcomes

5-state

Automated entitlement funnel

Server-verified

Subscriptions, no manual grants

One codebase

iOS + Android in beta