Build work / Scoped per shop

We cut the data. We also build the machinery.

The people who cut those files write software too, and three pieces of it are for sale to the shops that buy here: a read on a merchant’s application and bank statements, the wiring that keeps a pipeline current without anybody retyping it, and the shop’s own front door with an assistant answering on it. None of it is priced on a page.

Why a data desk is selling software

Because the calls stopped being about data a while ago. A shop rings for a count and ends up asking who reads the statements when two people are out, or why the same merchant is sitting in three reps’ pipelines with three different stories on him, or whether anything answers the site after six.

Each of the three below was built to answer one of those before it was ever offered to anybody — none of it is a prototype looking for a floor to try itself out on. What follows describes what each one hands you and then where it stops, in that order, because the second half is the half that decides whether you should buy it.

01 / The three lines

Three builds, and where each one stops.

They share nothing but a phone number. Take one, take two, take none of them and buy a file instead — they are not a suite and there is no version of this where they only work together.

  1. The statement read

    An application and a stack of bank statements in. One page of numbers out.

    You send the paperwork you already hold — the merchant’s application and the statements they handed you. What comes back is the page an underwriter would otherwise assemble by hand: what the deposits actually say the business turns over, set against what the application claims; how often the account came up short; how many days it sat below zero; which month the statements genuinely run through; and whether a month is missing or sitting in the pile twice. Underneath that, the things that get a file turned down, written as sentences a rep can read out loud without a translator.

    What comes back

    • Monthly revenue as the deposits show it, beside the figure the application states
    • How many items came back returned, and how many days the balance sat negative
    • The newest statement month in the pile, so the age of the picture is a fact rather than an assumption
    • Months that are missing, and months that arrived twice
    • The flags that get a file declined, each one pointing at the page it came off

    Where it stops

    • It decides nothing. No score, no grade, no yes and no no — your underwriter reads the page and makes the call.
    • It reads documents you already have. It goes looking for nothing about the merchant anywhere else, and it is not a report on anyone’s credit.
    • It reads what is on the paper. A statement that arrived as a photograph of a photograph reads worse than a clean export, and the page says so instead of filling the gap in.
    • It never speaks to the merchant, and it does not put a number on what anybody can have.
  2. Rep and CRM automation

    The retyping, handed to something that does not get bored of it.

    A deal gets entered once and then entered again four times — into the CRM, into the submission sheet, into a rep’s own tab, into the thread where the funder actually replied. That is where a pipeline goes stale. Not because nobody cares, but because the fifth copy is always the one nobody updates, and by Thursday the board and the truth have parted company. We build the wiring that carries it once: per-rep mail handled to a rule, new work landing on the right desk, the CRM and the tracker saying the same thing, and an approval or a decline filed against the deal it belongs to on the day it arrives.

    What we wire

    • Per-rep email automation — the routine mail a rep sends and receives, run to a rule instead of by hand
    • Lead routing and assignment, on whatever rule your floor already argues about
    • CRM syncing, so the board and the tracker stop disagreeing about the same deal
    • Submission tracking: what went out to whom, and when it went
    • Approval and decline capture, filed against the right deal without anyone retyping the terms

    Where it stops

    • It runs on the CRM you already have. Nobody here is selling you a platform or moving your shop onto one.
    • It cannot recover what was never captured. If an offer only ever existed in somebody’s head, no amount of syncing will find it.
    • Where a funder’s only door is a portal and a human being, it stays a portal and a human being.
    • It moves your pipeline around your own shop. None of what it touches becomes inventory here.
  3. The site, the assistant and the booking

    What somebody hits at ten at night, when nobody on your floor is going to pick up.

    Most funding shops have a site that was built once, by somebody who left, and has been quietly embarrassing them since. We build the working version: the pages themselves, an assistant that answers on them in your words, and a way to take a booking or an intake that does not end with a visitor downloading a form. The assistant knows what you hand it — your products, the states you work, the criteria you actually apply, your hours — and it answers out of that. The moment a question goes past what you gave it, it says so and fetches a person.

    What it includes

    • The site itself, written and built, on your domain
    • An AI assistant that answers from what you give it and sorts a visitor against your own criteria
    • Booking and intake that lands where your desk is already looking
    • The questions your desk asks anyway, asked once and in one place

    Where it stops

    • The assistant makes no offers. It does not quote a rate, a term or an amount, and it does not tell a merchant what they can get.
    • It answers from what it was given. Ask it something you never gave it and it hands over a person, because the alternative is a confident answer nobody at your shop would stand behind.
    • It is your site. The domain, the accounts and the code sit in your name, and the thing keeps working if you never ring us again.
    • We do not write your compliance language. What a page promises is your decision and your counsel’s.

02 / The terms

Four things that hold on every build

Scoped, then quoted once

There is no rate card for a build any more than there is one for a file. We talk about what your floor does today, the scope gets written down, and that scope gets one number. Nothing on this page carries a figure because no figure would survive contact with the next shop that calls.

You own the thing afterwards

The code, the accounts, the domain. A build that only keeps working while we are on the phone is a subscription wearing a project’s clothes, and you would be right to be suspicious of one.

Your deals stay your deals

A build runs on your merchants, your reps and your pipeline. None of it turns into records in a file we sell, and nobody else hears what your shop does on a Tuesday. That rule is not new here — it is the one we already sell data under.

No numbers about what it will do for you

We will tell you exactly what a build does and what it hands you. We will not tell you what it does to your turnaround, your close rate or your headcount, because nobody has measured that on your floor and a figure invented for a website is worth what you paid for it.

03 / Starting one

How a build starts

  1. 01

    One call, no deck

    Ring the number on this page and say which of the three it is and how the work gets done today. If you already buy files here it is the same number and the same person, and there is nothing new to sign to have the conversation.

  2. 02

    The scope gets written down

    What gets built, what it hands you, what it will not do, what we need from your side and in what order it is needed. You read that back and correct it before anybody agrees to anything.

  3. 03

    One number for that scope

    Quoted once, for the work in the scope. If the scope moves later that is a new number, and you hear it while it is still a question rather than on an invoice afterwards.

Rather put it in writing first? The contact page takes a brief, and it asks for no more of you than a sentence about what the floor needs.

Three builds, one line, and a scope written down before anybody agrees to anything. Say which one it is and what happens on your floor today.

(929) 513-2830