Skip to main content
Skip to content
About MoneyLoop

We build payroll for teams that didn’t know they needed it.

We were one of them.

Origin

How this got started.

We were running a three-person research lab and spending our Sundays on spreadsheets. The payroll tool we used charged us $80/month to write two checks. Onboarding a new hire took four days of PDFs, and the person we were onboarding had only agreed to a six-week project.

So we built this for ourselves first. One employee at a time. One week of timesheets at a time. We kept the bar dumb-simple: a payroll run you could finish between two meetings, an onboarding that a new hire could complete on their phone, a compliance log you would actually want an auditor to see.

Then our friends asked us to run theirs. Then their friends. We are a small team in Austin building for the kinds of teams we used to be — the two-person agency, the four-person lab, the owner who just made their first hire and does not yet know what an I-9 is.

Principles

Four rules we argue with ourselves about.

When a decision is hard, we come back to these. Sometimes they disagree with each other; that is usually where the product gets better.

Money moves, or it's broken.

Payroll has one job: pay people on the day you said you would. Everything else is details.

Compliance is design.

If your software makes it easy to do the wrong thing, that's a bug. W-4s, I-9s, state IDs — we design them in.

Small teams first.

We build for two-person startups and ten-person agencies — the teams other payroll apps quietly ignore.

No surprises on payday.

You see the numbers before the draft hits. Tax, deductions, net — no magic, no mystery.

Milestones

The boring version of the story.

Dates we actually hit, not dates we planned to.

  1. Founded in Austin

    Two engineers and a spreadsheet. We had been running payroll ourselves for a small lab and decided to rebuild it from scratch.

  2. First payroll workspace

    The first useful version could invite a teammate, collect their paperwork, and make the payroll numbers visible before anyone clicked approve.

  3. Security controls first

    We moved sensitive fields behind encryption, tightened role isolation, and made audit history part of the product instead of a spreadsheet.

  4. Provider gates by design

    Payroll release, tax filing, and bank movement stay unavailable until the right providers and account setup are actually present.

  5. Small-team HR OS

    Onboarding, time, documents, contractor payables, banking readiness, and payroll preparation are converging into one operator-friendly workspace.

The founding team

A small team building for small teams.

No invented logos, no compliance theater. Just product work that makes payday and onboarding less fragile.

  • PL

    Product lead

    Product operations

    Owns the operator experience: fewer dead ends, clearer setup gates, and fewer places for paperwork to disappear.

  • EL

    Engineering lead

    Systems and security

    Owns the data model, role boundaries, encrypted fields, and the parts of payroll that have to be boringly correct.

  • CA

    Compliance advisor

    Payroll and HR controls

    Keeps provider-gated claims gated, sensitive workflows documented, and compliance copy grounded in what is actually live.

  • DL

    Design lead

    Product experience

    Designs the parts people feel immediately: tab order, error recovery, information hierarchy, and trust in every form.

Hiring

We’re hiring for three roles.

Small team, sensitive workflows, high standards. If any of these sound like you, write us a line about something you’ve shipped.

hiring@moneyloop.ai

Prepare your first payroll draft with clean gates.

Start free. No credit card on the free tier.

No credit card on the free tier.

Back to home