Certain identifying details and artifacts have been omitted or generalized to preserve confidentiality.
The situation
Early customer-development work was spread across conversations, notes, and manual follow-ups. Pilot relationships needed a clearer path from first contact to follow-up, tailored proposal development, and conversion.
The approach
I designed a repeatable operating system across HubSpot, Notion, and n8n. The workflow connected relationship context, pipeline status, follow-up routines, and pilot materials so that customer-development work was easier to track and advance. I also built targeted automations for recurring tasks where structure and context could improve follow-up quality.
What I built
- a CRM-backed pipeline and lead-tracking workflow
- relationship-context records for more tailored outreach
- an AI-assisted partnership outreach generator that combines HubSpot deal data, Notion opportunity context, an LLM, and Gmail drafts
- a calendar-based workflow that prepares external meeting reminders and a daily summary
- a production lead-intake workflow that routes form submissions into HubSpot with Notion and Discord support
- reusable proposal and pilot materials
Why it matters
The work turned fragmented relationship management into a repeatable customer-development system. It demonstrates how I use lightweight automation to improve follow-through without losing the context needed for relationship-driven work.
Result
The broader customer-development effort included well over 100 customer conversations and resulted in two pilot partners signing letters of intent to use the product. The automations supported the operating system behind that work; they should not be read as the sole cause of the commercial outcomes.
What I learned
Customer-development automation is most useful when it preserves relationship context. The goal is not to automate every interaction. It is to make the right follow-up easier to execute at the right time.