Bookly started as a booking page and turned into the thing around the meeting.
If you make a living from conversations, scheduling was solved years ago. What is not solved is everything after the invite lands: remembering what the last call was about, taking notes while trying to listen, writing the follow-up at 11pm, and losing the one objection that decided the deal because nobody wrote it down.
The tools that exist for that are built for sales teams with a CRM admin. Bookly is built for the person who is the whole team: the consultant, coach, advisor or small agency who books their own calls and keeps their own relationships.
Scheduling is the entry point. Around it, Bookly keeps one record per person, briefs you before every call from that record, transcribes the call with consent when you use the Bookly video, and turns the transcript into a recap you can act on in one click: tasks, a stage change, a follow-up email. Your calendar can tell the difference between a customer and a cold lead, and defend your focus time from the latter.
Client conversations are the most sensitive data a small business has. That is why Bookly is released under the AGPL-3.0 and can run entirely on your own server, with transcripts and contacts in your own database and the AI features optional. The hosted version exists for people who would rather not run servers; it runs the same code.
Bookly is built by Ahmad Hakroosh, an independent software engineer, and operated by Cloudeo Solutions, LLC. It is developed in the open on GitHub, where the roadmap, issues and changelog live.
Questions, ideas or a story about a meeting that went wrong? Get in touch.