The irritation
CRM users repeatedly ask administrators how their company expects a field, process, or record to be handled, even when the answer exists somewhere in ignored documentation.
ProductRetiredRetired
Fondsworth
A retired AI HubSpot butler that answered company-specific CRM questions directly inside contact, company, deal, and ticket records.
- Current state
- Retired — Retired
- Jack’s role
- Product design, AI engineering, HubSpot extension development, Operations
- Find it in the workshop
- Archive Yard · Elephant-butler marker
Built because…
The real build story.
What I built
I built a personalized AI sales-operations assistant that lived inside HubSpot record sidebars and answered questions according to each company’s own operating guidance.
The hard part
Company-specific answers have to stay grounded in the right portal’s material, remain useful inside a small extension surface, and avoid confidently inventing CRM policy.
Under the casing
Proof, not decoration.
Build evidence02 items
- A HubSpot sidebar extension across contact, company, deal, and ticket records
- Backend licensing, user access, PostgreSQL storage, billing, and email workflows
- HubSpot UI Extensions
- Node.js
- PostgreSQL
- OpenAI
- Stripe
- SendGrid
Scope of work
What I owned.
- Product design
- AI engineering
- HubSpot extension development
- Operations
No victory-lap math
Outcome and lesson.
Where it landed
Fondsworth was built as a functioning HubSpot product with licensing, billing, user access, and an elephant-butler identity. It is now retired.
What stayed
A friendly assistant does not remove the trust problem. The quality of the company source material and the system’s willingness to admit uncertainty determine whether the answer helps.
Field notes
This project has a physical address.
In the playable workshop, Fondsworth lives in the Archive Yard as a elephant-butler marker. You can inspect it without unlocking anything.