The problem
Lead applications needed to become actionable sales workflows. A score alone was not enough: it needed to connect to follow-up questions, calendar destinations and CRM records.
I worked directly under the technical CEO, first as a full-stack developer and later as technical team lead. This work sat alongside backend systems, payments, HubSpot synchronization and operational automation.
What I did
I used models to interpret application answers and kept routing decisions in backend business rules.
I connected application submissions to AI-assisted scoring, backend routing and HubSpot updates, and built workflows, forms and failed-payment follow-up tasks.
Technical details
The system integrated OpenAI, Grok and LangChain into the lead qualification process.
Model-assisted interpretation produced a qualification score from 1 to 4.
Explicit backend business rules then selected the appropriate destination:
- Score 1: Free community
- Score 2: Additional qualification and potential setter-calendar routing
- Scores 3–4: Closer calendars
The backend also synchronized lead data with HubSpot and supported operational workflows, including failed-payment follow-up tasks.
Qualification workflow
- Application answers
- OpenAI / Grok via LangChain
- Score 1–4
- Backend routing rules
Operational destinations
- Free community / follow-up / calendar
- HubSpot updates and workflows
- Operations follow-up
The model interpreted application answers; backend rules controlled routing.
The result
Delivered a production qualification workflow connecting application submissions, AI-assisted scoring, deterministic business rules, calendar routing and HubSpot CRM automation.