The irritation
A scheduling link can look healthy while quietly offering no usable times, leaving sales and service teams to discover the problem after a prospect does.
ProductBuildingIn development
BookableCheck
A prelaunch service that checks public scheduling links and turns availability into useful HubSpot signals.
- Current state
- Building — In development
- Jack’s role
- Product design, Cloud engineering, HubSpot integration
- Find it in the workshop
- Systems & Maps Lab · Availability board
Built because…
The real build story.
What I built
I built a queued checker that inspects public scheduling availability, records a clear status, and makes that signal useful inside HubSpot workflows.
The hard part
Availability pages vary, change, and fail in ambiguous ways, so the checker must distinguish an empty calendar from a broken page or temporary network problem.
Under the casing
Proof, not decoration.
Build evidence02 items
- Queued availability checks with explicit result states
- HubSpot-facing signals backed by D1 and Workers
- Cloudflare Workers
- Hono
- D1
- Queues
- HubSpot
- Stripe
Scope of work
What I owned.
- Product design
- Cloud engineering
- HubSpot integration
No victory-lap math
Outcome and lesson.
Where it landed
BookableCheck is in development. Its staged application and operational architecture work, while launch and distribution work remain deliberately unfinished.
What stayed
A monitoring result is only useful when it explains uncertainty. In-development software should state what remains unfinished instead of borrowing credibility from the finished pieces.
This project has a physical address.
In the playable workshop, BookableCheck lives in the Systems & Maps Lab as a availability board. You can inspect it without unlocking anything.