01 / 02
Problem, then waitlist
The hero names the job — stop being the OTP machine — and captures teams before the product opens.

OctaVertex Media
Shared tool accounts send every OTP to one inbox. HeyPass routes the code to the person who asked — without handing them the mailbox. The waitlist product is live at heypass.io.

HeyPass
SaaS / Security Ops
How they reached us
The brief started inside our own studio: one person owned the ChatGPT / analytics / ads logins, and the rest of the team became a Slack bot for six-digit codes. We wrote the product for that person, then built the public site as a waitlist so teams could join before we opened seats. No card. No enterprise theatre.
The challenge
Password managers solve the password. They do not solve the verification email, the one-time link, or the 'is this you?' browser prompt that still lands in a single inbox. Giving the team the mailbox password was the unsafe workaround. Asking someone on a call to 'send the code' was the slow one.
Our solution
We designed HeyPass around forwarding, not mailbox OAuth: a rule the admin sets and can remove. Codes, links, and approvals are held briefly; everything else is deleted on a timer; the request log is the only durable record. The site has two stories — the inbox owner and the person who used to ask — plus a plain-language trust model (what we store, for how long, what we never open). Pricing is free for small teams at open, with a later Team plan.
Live waitlist at heypass.io with a second entry page for requesters
Trust model written as product, not a privacy policy afterthought
Forwarding-based architecture — no mailbox password on our servers
Per-account access that can be revoked the same minute someone leaves
A public comparison of 'how it goes now' versus the product, in the hero
The site
Captured at a desktop viewport from heypass.io — the interface buyers and operators actually use.
01 / 02
The hero names the job — stop being the OTP machine — and captures teams before the product opens.

02 / 02
A dedicated page for the person who used to Slack for codes, so the product has two entry narratives.


We researched, planned and developed a coconut-products storefront built around repeat delivery: shoppers can compare pack sizes, choose a coconut water subscription, and check Pune delivery details before booking.
Read Case Study
We researched, planned and developed VertexPOS, an invitation-only restaurant POS beta that connects counter, captain and table ordering with kitchen status, settlement records and daily reports.
Read Case Study
HealthyOme was selling dietitian-designed meals over WhatsApp and phone calls. We engineered a complete cloud kitchen operating system — shop, subscriptions, payments, kitchen ops, and growth automation — now live at healthyome.in.
Read Case Study