Skip to content

CRM Cleaning API

Prepares messy lead lists for CRM import.

Normalizes email and phone fields, finds duplicates and produces a quality report.

For
Sales operations and CRM teams
Engine
Rust (Axum) · Python
Source code
Closed · shown during a pilot
Buying
Written, fixed-price pilot

What is CRM Cleaning API?

CRM Cleaning API is a closed-source service that cleans messy lead lists before they are imported into a CRM. It normalizes email and phone fields (phones to E.164 where possible), finds duplicates, neutralizes formula injection and produces a quality report. It is written in Rust (Axum) and ships an OpenAPI schema.

A messy lead list, made ready for import.

5 rows, before CRM import

nameemailphone
Ayşe Yılmaz AYSE.YILMAZ@Firma.COM 0532 111 22 33
Mehmet Kayamehmet.kaya@firma(0212) 555 01 02
=HYPERLINK("http://x")info@ornek.com+90 533 444 55 66
Ayşe Yılmazayse.yilmaz@firma.com05321112233
Zeynep AkZeynep@AK.com.tr+44 20 7946 0958

Visualisation. The rules match the CRM Cleaning API code: cells starting with '=' or '@' are quoted, as are '+'/'-' cells that are not numbers; signed numbers are kept.

How it works

From the product's own documentation. Each number says where and on which version it was measured.

  1. CSV or JSON in

    A file upload or a record list. It is profiled first: missing values, types, duplicates.

  2. Fields are normalized

    Emails lower-cased, phone numbers converted to E.164, stray whitespace removed.

  3. Risk is removed

    Duplicates found by the keys you choose. Cells that a spreadsheet would run as formulas are neutralized.

  4. A report comes out

    Invalid emails and phones are flagged. A quality report is rendered to PDF with Typst.

E.164
Phone numbers converted to the international standard where possible.
Formula guard
Cells starting with '=' or '@' are neutralized. Signed numbers like '+44 20…' are left intact.
Repeat-safe
Idempotency keys, request IDs, rate limits and an audit trail.
OpenAPI
Every endpoint has a schema, ready to plug into existing automation.

Stack

  • Python
  • FastAPI
  • Pydantic
  • Typst
  • Docker

What it does not claim

Data schema, permissions and retention are agreed during the pilot.

Current boundary

Data schema, permissions and retention are agreed during the pilot.

What a pilot covers

A sample starting scope. Final deliverables and acceptance criteria are fixed in the written proposal.

Question
Can this lead list be imported with confidence?
Likely input
Permitted CSV records, field schema and merge rules
Deliverables
  • Normalized sample data
  • Duplicate and invalid record report
  • Import acceptance rules
Send your problem

Before you decide

Can I buy this product today?

A paid pilot and setup proposal can be prepared. Scope, data access, deliverables, timeline and a fixed price are agreed in writing after a discovery call.

Why is there no price?

Data volume, integration and success criteria differ from job to job. After the call you get a fixed-price written proposal; no paid work starts without your approval.

Do I need to upload live data here?

No. This site has no file upload or accounts. Data access, retention and permissions are set only in the pilot agreement.

What is the first step?

Choose CRM Cleaning API in the form and describe the problem you need to solve. The data and pilot boundaries are then set together.

  • ProofFrame

    Data contracts with verifiable quality evidence.

    Rust · Python · WASM
  • Fuzzy Dedupe

    Near-duplicate detection for names and organizations.

    Rust · Python
  • Scraping Pipeline

    Turns public web data into validated output.

    Python · asyncio