in early access · accepting design partners

For Indian B2B SaaS teams with 2–5 SDRs and 20–200 inbound leads a month.

Hi — I'm Krishan. I'm building a focused tool to handle the first touch on every inbound lead.

Acconvo qualifies the lead, sends a real first email from your team's address, and steps out of the way the moment your rep takes over.

At a startup I worked on previously, marketing was generating 100+ inbound leads a day. With three SDRs, we couldn't pretend to keep up — we'd cherry-pick by company name and rankings, send generic templates to the rest, and watch the bulk go cold or to a competitor inside two weeks. I'm building Acconvo so the next team doesn't have to choose which leads to ignore.

the lifecycle

What happens between “new lead in HubSpot” and “meeting on the rep's calendar”.

No magic boxes. Five steps, three exits, one loop. Every box maps to actual code you can read in our dashboard.

  1. 01
    INGEST

    Lead arrives

    HubSpot fires its contact.creation webhook the moment your form is submitted or your rep adds a contact. We pick it up in under 2 seconds — with the associated company record, source, and full property set already loaded.

    POST  /functions/v1/webhooks-hubspot
      event: contact.creation
  2. 02
    COMPOSE

    First email is drafted from your knowledge base

    An LLM call drafts the email using your product description, tone guide, objection playbook, CTAs, and proof points. Nothing else. No generic templates, no fabricated stats. Then it's sent from your team's Gmail, signed by the rep this lead is assigned to.

    gmail.users.messages.send → 200 OK
  3. 03
    LISTEN

    We watch for a reply

    Gmail Pub/Sub pushes any reply back to us in real time. Email opens are tracked. If the lead never replies, a configurable revival sequence kicks in — usually a touch at day 3, day 30, day 60, day 90, then archive.

    WAIT  reply | open | timeout=90d
  4. 04
    DECIDE

    Intent is classified, score updated, CRM synced

    When a reply lands, an LLM call classifies it — interested, objection, question, pricing, not interested, unsubscribe. The lead's score moves and the new score + status are written back to HubSpot via the bidirectional sync.

    PATCH /crm/v3/objects/contacts/:id
      acconvo_score, acconvo_status
  5. 05
    RESPONDLOOPS

    KB lookup → response → back to listening

    Objection? It's matched to your KB and answered with the reframe you wrote. Pricing question? Answered with your numbers. Then the loop closes — back to step 03, watching for the next reply, up to your configured turn limit.

    ↻  loop until exit condition met
EXITS
Lead agrees to meet

Handoff to your rep with full conversation, score history, and the recommended next step.

Lead opts out / not interested

Stops immediately. Re-touched on the revival schedule (day 3, 30, 60, 90), then archived.

Your rep replies in HubSpot

Automation pauses on this lead the same minute. We never talk over your team.

why this exists

The problem

Inbound is mostly a speed problem. A well-cited Harvard Business Review study (Oldroyd, 2011) found leads contacted within an hour qualify roughly 7xbetter than leads contacted just an hour later. Lean SDR teams can't hit that bar consistently — reps are in demos, follow-ups, and pipeline reviews. Inbound forms get answered when someone has 20 minutes. By then, half the leads have already moved on.

constraints

What we won't do

Four hard constraints. We hold these even when they cost us a feature pitch.

  • We never send a message without logging it to your CRM.

    Every email Acconvo sends shows up in HubSpot, on the contact, with the full body. You see what we said.

  • We never talk over your team.

    The moment your rep replies, our automation pauses on that lead. We're not going to send a follow-up while your rep is in the middle of a conversation.

  • We never invent facts about your leads.

    Every claim in an Acconvo email comes from your CRM, your knowledge base, or something the lead said. No fabricated stats, no made-up industry references.

  • We never put a hidden ops team behind the AI.

    The AI does the work. Nobody is in a back room rewriting emails to look smarter than the model is. You can audit every decision in your dashboard.

status

Where we are, honestly

Acconvo is in early access. Today: zero customers. I'm running a design-partner program — free for 30 days, extendable as long as we're delivering value, in exchange for honest feedback and (when you've seen enough to give one) a short testimonial.

SHIPPED
  • HubSpot integration via private app — webhook ingest + bidirectional sync
  • Company data auto-pulled from associated HubSpot Company records
  • Gmail send + reply detection (your domain, your signature)
  • Configurable scoring rules (title, source, industry, company size)
  • Configurable revival sequences with safe defaults
  • Per-client knowledge base, tone, and refusals
  • Real-time lead dashboard
  • Bounce + unsubscribe handling, automatic pause on rep activity
NOT YET
  • WhatsApp outreach
    We deferred it. The Meta Business / BSP setup is a project on its own and we'd rather not ship it half-done.
  • Zoho
    HubSpot only for now.
  • SOC 2 / formal compliance certifications
    We're a two-person team. Happy to sign a DPA you draft.

If that tradeoff works for you — early product, no price, founders on the other end of the email — we'd like to talk.

under the hood

Boring, well-chosen pieces.

We didn't reinvent the wheel. We picked a small set of well-understood tools and wrote thin, careful code on top.

Supabase Edge Functions
Deno · the webhook + decision layer
OpenAI (GPT-4 class)
Composition + intent classification
HubSpot Private App
Bidirectional CRM sync
Gmail API
Outbound + reply detection via Pub/Sub

the team

Two people. The ones building it are the ones you talk to.

K
Krishan Agarwal · engineering

I write all the code, run the infrastructure, and answer your support emails. If something is broken, I'm the one fixing it.

A
Ankita Agarwal · operations & customer

She runs onboarding, helps you set up the knowledge base, and is the human in your loop. The Calendly above is hers — when you book an intro, you're talking to her.

If you're an Indian B2B SaaS team with the inbound problem above, we'd like to talk.

Book a 30-min intro

Or email krishan@acconvo.com directly — both reach the same place.