Why I founded Rebban

I’m Jonathan Elgh, and I founded Rebban for a simple reason: freelancing shouldn’t mean running five half-connected systems just to get from “yes” to “paid.”

I’ve seen the pattern too many times—in my own work and in conversations with freelancers who were excellent at the craft and exhausted by the admin around it. The proposal lived in a doc. The tasks lived in a board. The hours lived in a timer. The invoice lived somewhere else. And payment follow-up lived in that awkward corner of your brain you try not to visit.

The problem wasn’t the work. It was the handoffs.

Every handoff leaked something. Scope got rewritten. Hours got orphaned. Invoice line items got approximated from memory. None of it felt dramatic in the moment. Over a month, it showed up as unpaid work, delayed cash, and a constant low-grade feeling that the business side was always slightly broken.

That’s the struggle I couldn’t ignore. Freelancers don’t need more complexity. They need fewer places where the story of a client engagement can fall apart.

I didn’t want to build a bigger stack. I wanted one loop that stayed connected: proposal → project → tracked time → invoice → paid.

What I kept seeing freelancers lose

• Clear agreements that never quite become real projects — scope creep starts early
• Delivery scattered across tools until billing becomes guesswork — when work lives in five apps
• Hours that were worked but never invoiced — the billable hours you never invoice
• Payment follow-ups that depend on awkward personal emails — tired of chasing clients for payment?

Those aren’t separate product categories to me. They’re chapters of the same freelance week. And if your tools treat them as separate, you end up doing the integration work yourself—every single time.

So I built the loop I wished existed

Rebban is built around that full path. Start with a clear proposal clients can accept online. Turn accepted work into projects and tasks. Track time against the work that actually happened. Create invoices from what already exists, then let reminders help you get paid without turning into a collections department.

That sounds obvious when you say it out loud. But most freelancers are still stitching it together by hand—and paying for that stitch work with evenings, weekends, and forgotten revenue.

Why this matters to me personally

I care about freelancers who want to stay independent without building a tiny operations department around themselves. The goal isn’t to make admin exciting. The goal is to make it quiet—so more of your week can go to the work clients actually hire you for.

If you’ve ever finished a strong project week and still felt behind on billing, you already know the feeling that started Rebban. I wrote more about that exact drain in Freelance admin is eating your billable week.

From proposal to paid—on purpose

Rebban exists because I believe freelancers deserve software that respects the whole engagement, not just one slice of it. Clear agreements. Visible delivery. Hours that become invoices. Follow-up that doesn’t depend on perfect memory.

If that resonates, start on the homepage, or jump into the part of the loop that hurts most today. I’m building Rebban for the freelancers who are done rebuilding the same client story in five places.

— Jonathan Elgh, founder of Rebban