The irritation
Knowing a contact’s local time should not require opening another tab, translating a location, or doing arithmetic before every call.
ProductReleasedActive product
What Time Is It? V2
A HubSpot application that makes object-local time visible across teams, records, languages, and time zones.
- Current state
- Released — Active product
- Jack’s role
- Product design, Backend engineering, Localization
- Find it in the workshop
- Systems & Maps Lab · Timezone station
Built because…
The real build story.
What I built
I built a paid HubSpot application that writes useful time context onto multiple CRM object types and presents it across seventeen languages.
The hard part
Time zones combine changing political rules, incomplete location data, daylight-saving transitions, localization, and asynchronous CRM updates.
Under the casing
Proof, not decoration.
Build evidence02 items
- Local-time context across multiple HubSpot object types
- Localized output across seventeen languages
- Node.js
- Cloud Run
- Firestore
- Stripe
- SendGrid
- HubSpot
Scope of work
What I owned.
- Product design
- Backend engineering
- Localization
No victory-lap math
Outcome and lesson.
Where it landed
The result is an operated application with billing, messaging, and infrastructure around a very specific everyday workflow problem.
What stayed
Time is a data-quality problem disguised as a formatting problem. Good automation keeps its assumptions visible when location evidence is incomplete.
Field notes
This project has a physical address.
In the playable workshop, What Time Is It? V2 lives in the Systems & Maps Lab as a timezone station. You can inspect it without unlocking anything.