A product with a real operation behind it.
Biolev needed a platform around health-test kits. Customers registered kits and followed their status. Stores invited and supported customers. Administrators resolved exceptions. Lab events needed to reach the right workflow, and communications had to be timely and traceable.
Bhavin worked with the operating team to map those responsibilities before defining the software boundaries.
Connect the lifecycle.
The implementation centered on a test kit and its state, with distinct customer, store, and administrator interfaces. Store-scoped access reflected real ownership rather than treating every user as the same kind of account.
Incoming lab events were validated and queued. Background processing resolved the kit, updated its lifecycle, and triggered the appropriate follow-up. Out-of-order events and cases awaiting a customer record had explicit handling.
Make communication inspectable.
Notifications were processed asynchronously with records of their recipient, provider, and delivery state. Sensitive exceptions could produce a draft for an operator to review before customer communication.
The implementation combined Cloudflare Workers, Queues, D1, R2, and other application services. It gave the business connected workflows and administrative tools to handle routine exceptions without making each one an engineering task.
The broader lesson
Useful automation starts with the real process, including its exceptional cases. Clear ownership, durable state, and reviewed actions can matter as much as the interface the customer sees.