TITAN BOOKINGS
An integrated booking tool for businesses — built within Titan to help them turn conversations into clients.
PROJECT OVERVIEW
This was a 0 to 1 feature built in under 3 months.
I led design end-to-end from early research and scoping to wireframes, prototypes, and final UI. I worked closely with a product manager and a team of 4 engineers.
Our goal was to validate, design and ship a built-in scheduling tool that fit naturally into the Titan Mail experience.
ABOUT TITAN MAIL
Titan is a communication suite built for small businesses. It brings together Mail, Calendar and Contacts in one focused space. Most of our users are service providers like consultants, coaches and freelancers who run their business from their inbox.
Titan helps them stay organized, save time and grow faster.
Our users were already running their business from Titan Mail. We saw an opportunity to bring scheduling into the same space—no third-party tools, just one seamless flow from email and calendar to appointments.
How a simple test validated our idea
VALIDATION TEST
We placed a question inside Titan Mail: “Would you use a built-in appointment booking tool?”
Further synthesis of 275 responses received uncovered:
Common use cases - consultations, demos, follow-ups
Frustrations with existing tools
Feature requests across industries and team sizes
Clicked on "Not interested"
Clicked on "Join the free beta"
Results of this test helped us move forward with our hypothesis. The data collected from the test helped us define personas and prioritise the first version of Titan Bookings.
Defining the goal
We wanted to build fast, learn quickly, and stay focused on real user needs. The goals were clear on both sides.
BUSINESS GOALS
Increase engagement by expanding the Titan ecosystem
Launch a lightweight MVP to test product-market fit
Enter a high-demand category with strong monetization potential
Drive organic growth by solving a universal pain point
USER GOALS
Eliminate back-and-forth in scheduling
Make it easier to win leads and close deals
Offer a built-in alternative to external tools
Scoping what to build
RESEARCH
We didn’t want to clone tools like Calendly. We wanted to build something focused and native to Titan users. To get there, we combined competitive analysis with qualitative insights.
We studied leading tools to understand how they priced, positioned and packaged features. We also mined user reviews on Capterra and G2 uncover what people loved, and what frustrated them.
THIS HELPED US DEFINE:
What our MVP should include
What to deliberately leave out
What personas to design for first (and which to support later)
Wireframes
With scope defined, I moved into wireframing. These helped clarify structure, flows and logic before we got into the weeds of UI. I mapped the core booking experience end-to-end, from creating a service to managing availability and access.
The wireframes also helped us estimate effort, catch edge cases early, and align on what we’d ship in v1.
Final visual designs
WHAT NEXT?
Once the flows were locked, I moved into high-fidelity designs. The focus was on keeping things clean, familiar and fast to use — especially for busy service providers. Every screen was built to feel native to Titan, while reducing the friction of scheduling to just a few clicks.
FINAL DESIGN JOURNEY
Onboarding with booking page setup
Calendar and availability management
Service creation and booking controls
Public-facing booking and confirmation pages
ONBOARDING
Choose a personalised URL and creating a booking page. Next select calendars to block busy times for when clients book a time.
SERVICE CREATION
Adding details about the service offered, setting up availability and host for the service.
BOOKINGS
Adding details about the service offered, setting up availability and host for the service.
VISITOR SIDE BOOKING PAGE
Adding details about the service offered, setting up availability and host for the service.
To gather feedback quickly, I created an interactive prototype in Figma and tested it using Maze. We started with internal testers who frequently schedule meetings, but external response was low.
To solve this, we re-ran a fake door — this time saying Titan Bookings was live. Users who clicked were redirected to the Maze test.
THIS LED TO
60+ recorded sessions
Rich feedback through heatmaps, clicks and voice notes
I analyzed these responses, identified usability gaps and incorporated the changes into the final design, ready for development.
Business impact and metrics
IN THE FIRST MONTH
Titan Bookings went live with two early partners. While not all were ready to adopt immediately, the early signals were strong.
5,766
booking pages created
8,840
services were set up
2,059
services with bookings
These numbers validate the core need. More importantly, they showed how tightly scheduling could integrate into the existing Titan workflow.
Key learnings and future scope
FUTURE SCOPE
This project was a crash course in building fast and learning faster. Testing early, even with something as simple as a fake door, gave us direction and saved weeks of guesswork.
Great ideas can stall without internal support and timely execution. As we scale Titan Bookings, the focus is on supporting more personas and advanced scheduling needs, while keeping the experience simple and tightly connected to Titan Mail and Calendar.
This project showed me that valuable insights don’t always come from polished prototypes. Sometimes, small experiments lead to the biggest clarity.
Here you'll only find
isha.designworks@gmail.com