Some parts of this page need JavaScript.

Skip to main content

Analytics only if you accept. Privacy

All work

Sales & Marketing / Case study

Verrow

Lead data quality workbench

Verrow running
Verrow

In short

Verrow is a public lead-data workbench: it ingests raw CSV lead files, suggests column mappings and lets a person review them. Quality scoring and dashboards are UI prototypes.

Visibility
Public GitHub
Focus
Lead data quality
Stack
React, Vite, Rust
Built with
TypeScript / React / Vite / Rust / SpacetimeDB / CSV Processing

Inside the project

01 / 03

The dashboard, a UI prototype.

Verrow1 / 3

Verrow dashboard showing ten uploaded files, 2,847 records, recent activity and data insights

The dashboard, a UI prototype.

The brief

The problem

Lead lists are often messy, duplicated and incomplete. Teams import them into CRMs before checking data quality, then clean up afterwards.

What we did

Our approach

Built a Vite and TypeScript workbench with a Rust ingest API that treats lead files as operational data: upload a CSV, inspect its columns, and review suggested mappings before processing. Quality scoring and dashboards exist as UI prototypes.

Features

What it does

  • Raw lead file intake

  • Column-mapping suggestions

  • Mapping review before processing

  • Standard lead schema

  • Reviewable source code

Results

What happened

  • Public GitHub project
  • CSV ingestion with column-mapping suggestions
  • Typed workflow with a review step for each file
  • Quality scoring and dashboards built as UI prototypes

Architecture

Under the hood

Lead-data workbench that takes raw CSV files through mapping suggestions to human review.

frontend
backend
database
external
ImportPreview and mapBridge in progress
Raw Lead Files
CSV and exported lists
Review UI
React/Vite interface
Rust Ingest API
Upload, preview and mapping suggestions
SpacetimeDB
Uploads, mappings and jobs

Lead-data workbench that takes raw CSV files through mapping suggestions to human review.

Services

What this work shows we do

  • Lead generation

    Leads found, cleaned and routed to the right person.

    Service page
  • Business automation

    Repetitive steps moved to code that runs the same way every time.

    Service page
  • CRM

    A CRM set up around your pipeline, connected to the rest of the stack.

    Service page

Related work

Built with the same services

Other work of ours that shares this project's services.
  • ButlerCRM, running
    Business Systems

    ButlerCRM

    ButlerCRM keeps contacts, deals, email, calendar and tasks in one workspace that updates live for everyone in it. We rebuilt it on Elixir/Phoenix so changes appear for the whole team as they happen.

    Read the case study
  • TraceKill, running
    Privacy & Security

    TraceKill

    TraceKill is a live privacy product. It scans data-broker sites for a person's information, files the removal requests, and keeps checking because the data tends to come back.

    Read the case study

How we work

How a change reaches production

The same five gates for our own products and for yours. Nothing reaches your customers on the strength of a demo.

  1. 01 · Isolate

    Its own branch and workspace

    Every change starts in a separate copy of the code, so work in progress never touches what is live.

    git worktree add .worktrees/your-change
  2. 02 · Build

    Engineers with AI agents

    Agents write and test code beside us. They hold no passwords: every call they make goes through our gateway, which checks it and logs it.

    agent → gateway → policy · audit · call
  3. 03 · Prove

    Evidence, then review

    Tests, before-and-after screenshots of the running app, then independent reviewers. It does not move on until no serious finding is left.

    review: 0 high · 0 medium → pass
  4. 04 · Ship

    Deployed and checked live

    The pipeline builds and deploys. Then we check the running service itself, not just a green build.

    replicas 1/1 · image sha matches · health 200
  5. 05 · Watch

    Checked every night

    Each integration we run is tested against its provider every night, so a changed API is caught before your team notices.

    nightly: each integration vs its provider

Want something built like this?

Tell us what your team does by hand and the tools involved. Lead generation is where most projects like this start.