← All work

CloseCalls

A booked call still has a long way to go.

Someone fills in a form, finds a slot, and books a call. There is still a lot that has to happen before that becomes a useful conversation. CloseCalls pulled me into working through that whole journey.

My work

Product & integrations

The chapter

Side project

Explore CloseCalls
CloseCalls illustration of answers being saved as a person fills in a form
Lead capture, as illustrated on the CloseCalls landing page. Source ↗

Looking at the spaces between the steps.

The product connects lead capture, qualification, scheduling, reminders, and follow-up. My work has moved across the customer journey, integration planning, and coordination with the people designing and building it.

That meant getting specific about forms and calendars: what should happen when someone leaves a form halfway through, how a lead should be routed, and what the team needs to know before a call.

Making it easier to connect.

One thread was the connection with tools clients already use, including GHL. I worked through OAuth, Pipedream Connect, and webhooks, with a simple question in mind: how much of this setup should a customer really have to understand?

I also helped shape the UI/UX engagement across onboarding, forms, scheduling, and analytics, including the scope, milestones, and review rhythm.

CloseCalls lead qualification and routing product illustration
Qualification and routing.
CloseCalls follow-up and CRM product illustration
What happens after the call.

Product illustrations from the CloseCalls landing page; shown to explain the experience.

Staying with the product.

The brief, the interface, the integration, and the testing all affect one another. I have been involved across those conversations, following the details as the product took shape.

CloseCalls is collaborative work. This page shows the product we have been working on and the parts I have helped move forward.