Custom CRM development

A custom CRM and sales engine, built around how you actually sell

Generic CRMs make you work their way and charge per seat for features you don't use. We build the CRM your process needs: leads from the sources that matter to you, enriched and verified, outreach drafted by AI and approved by people, replies sorted automatically. We built one to sell our own products.

  • Leads enriched from several sources, with every source kept
  • AI-drafted emails that a person approves before they're sent
  • Replies classified, opt-outs suppressed everywhere at once

Sales pipeline

  1. Collect

    Import leads from public business data, websites and your existing lists, with one record per source.

  2. Enrich and verify

    Fill in company details and contacts, and verify email addresses before anyone spends time on them.

  3. Draft

    AI writes a personal email per contact, following the campaign brief.

    • campaign brief
    • follow-ups
  4. Approve and send

    A person approves each email. Sending is paced per mailbox and follow-ups stay in the same thread.

  5. Handle replies

    Inboxes sync automatically, and replies are matched, classified and routed.

  6. Measure

    A funnel per campaign, from contacted to replied to customer.

The pipeline of the sales system we built for our own products.
What we can build

What we can build

A complete CRM, or a sales engine next to the CRM you already have.

A CRM on your data model

Companies, contacts, deals and statuses that match how you sell, with prospects kept separate from paying customers and a full event history.

Lead sourcing and enrichment

Imports from public business data, websites and your own lists, with one record per source, so you always know where a detail came from.

Email verification

Addresses checked before outreach, cached to save credits, and checked again just before sending to protect your sender reputation.

AI-drafted outreach

Personal emails drafted by AI from your research and campaign brief, with rules on the server that refuse drafts breaking your guidelines.

Sending from your own mailboxes

Email sent through Gmail or Google Workspace from your own addresses, with daily caps, send windows and natural spacing. No tracking pixels.

Reply handling

Inbox sync, bounce detection and reply classification, so opt-outs are honoured everywhere and interested replies reach a person fast.

Proof, not promises

The sales system behind our own products

We built a sales CRM to run outbound for our own products. An AI agent operates it through MCP and a person stays in control: research, enrichment, verification, drafting and reply handling run in the system, and nothing goes out without human approval.

It replaced a third-party outreach tool with in-house sending through the Gmail API, which gave us full control over pacing, threading and data.

  • Prospects and customers kept separate, with a full audit trail of every change
  • An opt-out always wins: it stops every campaign and cancels open drafts
  • Inboxes synced every five minutes, with hard, soft and forwarding bounces told apart
  • Ten reply categories, each with its own follow-up action
  • A funnel per campaign, from first email to paying customer

What happens when a reply comes in

  1. Inbox sync

    Every five minutes, each mailbox is mirrored into the CRM.

  2. Match

    The reply is tied to the right email and contact, with a confidence level for the match.

  3. Classify

    Ten categories, each with its own consequence on the server.

  4. Act

    Opt-outs are suppressed in every campaign and open drafts are cancelled. Interested replies go to a person with a suggested answer.

agent tools on the sales MCP server
35
reply categories with automatic actions
10
between inbox syncs
5 min
tracking pixels in outgoing email
0
Who it's for

Who we build this for

B2B companies with outbound sales

You sell to businesses and your team spends hours researching, writing and following up. We automate the legwork and leave the decisions with people.

Teams that outgrew their CRM

Custom fields and workarounds everywhere, and it still doesn't fit. A CRM built around your process removes the friction.

Companies paying too much per seat

When most users only need a few screens, a focused internal tool can cost less and fit better.

Businesses with data in many places

Leads in spreadsheets, a shared mailbox and an old CRM. We bring them together in one model with clear sources.

How it works

How we build your CRM

We start with your sales process, not with a feature list.

  1. 1

    Map the process

    Who you sell to, where leads come from, what a good lead looks like and every step until someone pays.

  2. 2

    Design the data model

    Companies, contacts, statuses and sources that fit that process, including what happens with opt-outs and duplicates.

  3. 3

    Connect the sources

    Importers and enrichment from the data sources that matter to you, built so a new import only fills in what's missing.

  4. 4

    Add AI where it saves hours

    Research summaries, drafts and reply classification, with rules on the server and a person approving anything that goes out.

  5. 5

    Send and sync safely

    Your own mailboxes, sensible pacing, bounce handling and suppression lists that protect your domain.

  6. 6

    Measure the funnel

    Conversion per campaign and per step, so you know what works and where leads drop off.

Tooling we use

Your CRM runs on the same stack as our products, with Google APIs for sending and syncing mail and an MCP server if you want an AI agent to operate it.

  • Ruby on Rails
  • Hotwire
  • PostgreSQL
  • Solid Queue
  • Gmail API
  • Google Workspace
  • Google Places API
  • OpenStreetMap
  • MillionVerifier
  • MCP
  • OpenAI
  • Claude
Cost & timeline

What does a custom CRM cost?

A focused CRM for one sales process is a very different project from replacing an enterprise suite. The estimate depends on:

Process complexity
One pipeline with a few statuses, or several teams, products and countries with their own rules.
Data sources
Each source needs an importer, matching and upkeep when the source changes.
Email and AI automation
Verification, drafting, sending, inbox sync and reply classification each add work, and each saves hours later.
Migration
Moving contacts and history out of spreadsheets or an existing CRM without losing context.
Integrations
Connections to your website, billing, support desk or accounting.
FAQ

Questions about a custom CRM

How much does a custom CRM cost?

It depends on the complexity of your sales process, the number of data sources and how much email and AI automation you want. After a free intro call you get a written scope and estimate, usually starting with the part of the process that costs your team the most time.

Why build a custom CRM instead of using HubSpot or Salesforce?

If a standard CRM fits your process, use it. Custom makes sense when you pay for many seats that only need a few screens, when your process doesn't fit their model, or when you want AI automation that standard tools don't allow.

Can AI write our sales emails?

AI can draft them from your research and campaign brief, and in our own system it does. A person approves every email before it's sent, and the server refuses drafts that break your rules.

Is automated outreach allowed under the GDPR?

That depends on who you contact, how and where. We build in the tools to do it carefully, such as verified business addresses, recorded sources, suppression lists and opt-outs that apply everywhere. Have your approach checked by a legal advisor as well.

Can it send from our own email addresses?

Yes. We send through the Gmail API from your Google Workspace mailboxes, with daily limits, send windows and natural spacing, and follow-ups in the same thread.

Can it work alongside our existing CRM?

Yes. We can build the sourcing, enrichment and outreach engine next to your current CRM and sync the results into it.

Tired of bending your CRM around your process?

Tell us how you sell today and where the hours go. You'll get an honest view on what to automate, what to keep and what it would take.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to