Skip to content
Velo.

About

Built in Brisbane.

Velo is a side-of-the-desk project that grew out of a frustration: freelancer tools are written for everyone except devs. So I'm building the one I'd actually want to use.

Why I'm building this

Built for devs who'd rather be coding.

Most freelancer tools feel like they were made for someone else: wedding planners, marketing consultants, designers. The interfaces are busy, the language is patronising, and the workflows assume a kind of work that isn't mine. Meanwhile, devs spend their day inside their editor, terminal, and GitHub. Clean, fast, well-designed tools. The business side of being a dev shouldn't feel like a step backwards from that.

Velo is for the dev who's tired of running their freelance work out of something that looks and feels like 2015 SaaS. No popups asking for testimonials, no badge-shaped CTAs, no clip art. Just the proposal-to-invoice flow, scoped for how dev work actually happens.

The team

The team.

Velo is built mostly by one person, with help from contributors who send PRs and feedback. No investors, no growth team, no quarterly OKRs.

My commitment

If I ever shut Velo down, your data comes with you.

I'll give you at least 60 days notice before Velo shuts down. No sudden surprises. You'll get an email with instructions and a download link for everything I hold for you.

Your export includes every proposal, invoice, client record, project, milestone, and time entry, in a standard format you can open without Velo. Nothing is locked in.

It's just me building this, and I'm honest about that. I'd rather tell you this upfront than have you find out at the worst possible moment.

Where I am

Known limits and what's next.

I'd rather show the seams than pretend they aren't there. Below: what doesn't exist yet, and the order I plan to build everything in.

Known limits.

Platform
  • Email sometimes lands in spam

    Sending from Resend's shared sender while I verify a custom domain.

  • No public API or webhooks

    You can't integrate Velo with your own tooling yet. A public API is on the roadmap.

  • No analytics or reporting yet

    Project and invoice views show current state but not trends. Revenue, profitability, and time-cost reports come later.

  • Mobile works but is desktop-first

    Functional on phones; designed for desktop first. Dedicated PWA polish is coming.

Team & CRM
  • Clients are a contact list, not a CRM

    Name, email, and phone today. Notes, tags, lead stages, last-contact tracking, and a communications log are the next thing I build.

  • No team roles or permissions yet

    Studio and Agency plans show seat counts, but owner / admin / member / viewer permissions haven't been built. Multi-user lands together with the access model.

  • No e-signature on proposals

    Client approval is a button click on the share link. Signed PDFs with timestamps come later.

  • No file attachments

    Milestones support deliverable links, but you can't upload contracts, receipts, or asset files to projects or invoices yet.

Money & billing
  • AUD and GST only

    Pricing, invoices, and tax handling assume Australian businesses. Multi-currency and non-AU tax regimes are a separate build.

  • No accounting software exports yet

    GST is calculated, but you'll need to copy numbers into Xero, MYOB, or QBO by hand. Native exports are planned.

  • No recurring invoices or retainers

    Every invoice is one-off. Monthly retainers and subscription billing are on the roadmap.

  • No automated payment reminders

    Invoices don't chase themselves. You'll nudge late-paying clients by hand until reminder workflows ship.

  • No expense tracking

    You can invoice clients but can't log business expenses, mileage, or reimbursables against a project.

Heads up
  • The product name might change

    "Velo" is a working name. The final name lands before public beta. Don't get attached.

What's next.

  1. 01

    Custom sending domain for email

    Verifying my own domain so proposals stop landing in client spam folders.

  2. 02

    CRM upgrade for clients

    Notes, tags, lead stages, and a communications log. The most-asked-for change in early feedback.

  3. 03

    Team workspaces and roles

    Multi-user accounts on Studio and Agency plans, with owner / admin / member / viewer permissions.

  4. 04

    Recurring invoices and retainers

    Monthly billing for ongoing work, not just one-off project invoices.

  5. 05

    File attachments on projects and invoices

    Upload contracts, receipts, and asset files instead of stuffing everything into deliverable links.

  6. 06

    Accounting software exports

    Native exports to Xero, MYOB, and QBO so end-of-quarter isn't a copy-paste job.

  7. 07

    Public API and webhooks

    For wiring Velo into your own tooling once the core flow is stable.

  8. 08

    Analytics and reporting

    Revenue, profitability, and time-cost views once there's enough data per account to be meaningful.

  9. 09

    Multi-currency and non-AU tax

    Pricing and tax handling beyond AUD/GST. Comes after the Australian core is solid.

Questions? Email me at jaineelk.dev@gmail.com. I read everything.

Trust

How I handle your data.

Velo handles proposals, invoices, and client records. Read the security page for the full picture, in plain language.

See security