Case study · Newgarden Ecosystems · Landscaping

    Six hours a week of check entry, gone.

    Newgarden mows about 30 lawns a day for 202 clients, and most of them pay by paper check. Every check was typed in twice. Now a scan goes in and a statement comes out.

    6 hrsa week

    of entry work back

    72checks

    on the first run, with 0 errors

    2.5¢per check

    in AI cost to read one

    The problem

    The same four numbers, typed twice, for every check.

    Not a broken process. A working one that ate a working day every week, and capped how many clients the business could take on.

    How it worked

    Before
    1. 1

      Check arrives in the mail

      Roughly 30 lawns a day, most of them paying by paper check.

    2. 2

      Someone photographs it

      Four or five checks to a photo, whenever there's a spare minute.

    3. 3

      Typed into the payments sheet

      Name, amount, check number, date.

    4. 4

      Typed again into the invoice sheet

      same numbers, twice

      The same four fields, a second time, so a statement can go out.

    5. 5

      Who paid? Worked out by hand

      Scan two sheets, compare, chase.

    How it works

    Now
    1. 1

      Check gets scanned

      Same scanner, same folder as before. Nothing new to learn.

    2. 2

      Read automatically

      Name, amount, check number and date come off the image.

    3. 3

      Matched to the client

      Against 202 accounts. Corrections teach it the next one.

    4. 4

      One tap to confirm

      A queue on her phone. Confirm, correct, or set aside.

    5. 5

      Statement goes out

      Balance, payments, and a tear-off slip, on her letterhead.

    What we built

    Follow one check through.

    Five stops. A person touches it once, at the fourth.

    Scan folder

    Checked every 15 minutes

    Read

    Every field off the image

    Match

    To one of 202 clients

    Confirm

    One tap on her phone

    Statement

    Out on her letterhead

    Where it lives

    Her data stays hers.

    It runs on a server set up for Newgarden alone, signs people in from her own domain, and sends statements under her own name. Compound built it. Compound doesn't hold it.

    Scanner folder

    Her existing shared folder

    Bank feed

    Read only

    Her own server
    • Dashboard
    • Review queue
    • Client ledger
    • Statements
    • Check images
    • Sign-in from her own domain

    Statements to clients

    Her letterhead, her sender

    Nightly backup

    To her own cloud folder

    Sound familiar?
    • Someone on your team retypes numbers from paper, PDFs or photos every week.
    • Two spreadsheets hold the same facts, and someone reconciles them by hand.
    • You know who hasn't paid because you remember, not because something tells you.
    See it running

    Twenty minutes. We'll walk you through it live.

    Bring the process that eats your week. We'll show you Newgarden's system and tell you honestly whether yours is the same shape.

    Book a demo call