
Accordio AI
AI contracts and payments for freelancers
Accordio started as a contract and invoice tool for freelancers. Web app. Dashboard. The usual.
A lot of people signed about but nobody paid...
The product worked... but nobody came back after the first contract. Makes sense. You don't create contracts every day.
So I stepped back and looked at what we actually had.
Contracts. Invoices. E-signatures. Payments with escrow. Time tracking. Client management. Risk analysis.
All the pieces were there... they were just sitting in a dashboard nobody opened.
Then I found OpenClaw. Clawdbot at the time.
Took it. Put it in a secure cloud environment. Connected all 79 tools we already built. Added persistent memory. Cron automation. Custom skill creation.
Now everything runs from one conversation.
WhatsApp. Telegram. Slack. You message it... it happens.
"Invoice Sarah for last week" ... done.
"What's overdue?" ... it knows.
"Remind me Friday to follow up with TechStart" ... scheduled.
The foundation was always there. It was just about connecting the puzzle pieces through one gateway... instead of another dashboard.
v2 is live.
Saw ClawdBot/Moltbot/OpenClaw... whatever u call it these days. And similar projects letting people chat with Claude through WhatsApp and Telegram...
And I thought: why are freelancers still opening apps to manage their business?
The magic of AI shouldn't require logging into a dashboard.
The insight:
Most people I talk to aren't scared of AI. They're scared of learning another tool.
But everyone already knows how to send a WhatsApp message.
"Create a contract for Sarah, $5k website project" → done.
"Send a payment reminder to Mike" → done.
"What's overdue this week?" → instant answer.
"How many hours did I work on the rebrand?" → pulled from automatic tracking.
No login. No dashboard.
No learning curve.
The problem with existing bridges:
Tools like OpenClaw/Moltbot are cool... but they're general purpose. They don't know your clients. Your contracts. Your invoices. Your rates.
And the security question is real. You're routing your computer data through third-party bridges you don't control.
What we're building:
WhatsApp and Telegram agents that connect directly to your Accordio account.
The AI knows your business context:
Every contract you've created
Every client and their history
Every invoice (paid and overdue)
Your rates, terms, preferences
Your tracked time (automatic... no timers, no logging)
The desktop app runs quietly in the background. Tracks what apps you're in, what projects you're working on. AI suggests where to bill it.
Then from WhatsApp: "Invoice Sarah for this week's work" → AI pulls the tracked hours, generates the invoice, sends it. Done.
Same AI. Same data. Just accessible from where you already are.
No sketchy middleware. No API keys to configure. Just scan a QR code and go.
Why this matters:
The freelancers I'm building for aren't technical. They're designers, writers, consultants.
They don't want to learn BotFather. They don't want to configure webhooks. They don't want to remember to start a timer every time they open Figma.
They just want to say "invoice Alex for last week's work" and have it happen.
That's the bar.
Still building this out. Curious if anyone else is thinking about messaging-first AI products... feels like the interface layer nobody's nailing yet.
9 integrations in... more to come (Notion, Trello, Clickup, Todoist, Jira, Slack, Drive, Linear, Asana).
Built Accordio for contracts. AI-generated, legally solid, get-paid-on-time kind of stuff...
Turns out... people are using it to write AI proposals from meeting notes.
They hop on a call, dump their notes into the AI, and get a full proposal draft in 2 minutes. The contract part comes after.
I spent months perfecting the contract flow. Users found their own workflow.
This is why positioning is the hardest part of building... even for niche apps. You think you know what problem you're solving. Then you watch someone use it and realize they're solving a different one.
Now leaning into it. Meeting notes → proposal → contract → payment. The full flow.
Still at 300ish users, still at €0 MRR. But the activation is finally clicking.
Sometimes you don't find product-market fit. Your users show you where it is.
1 Like
Comment
Week 1 we hit first 100 users. This week: 300. Uhuu...
Sounds like progress. Here's the reality from week 1:
37 fully completed onboarding
~16 created a contract
5 sent one to a client
0 paying users
The activations was broken. So I focused on that...
What worked for marketing:
TAAFT (There's An AI For That) - $325 for a listing, brought 361 sessions in a week. Still driving traffic daily. Best money I've spent so far.
LinkedIn organic - up 475% week-over-week. Building in public is actually working. 1,600+ followers now.
Cold email - 4 domains warming up. Launching in 2 weeks.
What didn't work:
X/Twitter - account suspended out of nowhere. No warning, no explanation. Lost $200 in unused ad credits and my Gold subscription. No refund. Just gone...
I had 20 followers. Just replying... What exactly was I doing wrong?
Product Hunt - launched with 7 upvotes. Completely invisible. Dead on arrival.
100 users means nothing if nobody activates. So I fixed the dashboard and onboarding. Lesson learned.
7 Likes
7 Comments
7 Comments
-
2
Congrats on the launch, looks solid. What channels are you experimenting with to get early users?
-
1
Was there anything in particular that you were posting on Twitter? Were the responses written by you or an AI bot? I'm just curious as I've heard of other accounts being closed a little overzealously recently.
Also, how are you doing the A/B testing on the onboarding?
All the best,
Andy.-
1
hey Andy, good questions
honestly... no idea why X suspended me. I had the golden freaking checkmark :)
was just posting founder journey stuff, building in public content. all written by me, no bots. had like 20 followers lol, wasn't exactly spamming... just replying a lotasked for a review, got denied, no real explanation. lost $200 in ad credits that were never even used. classic X moment
on A/B testing onboarding - keeping it scrappy for now. not running proper split tests yet... more like shipping changes, watching the numbers in PostHog, talking to users who drop off. "why didn't you create a contract?" type convos
once we have more volume we'll do proper A/B tests but at 300 users... qualitative feedback moves faster than statistical significance
thanks for asking, appreciate it
-
-
1
How are the activations doing now?
-
1
Way better now since I will be more positioning towards an agentic layer that does you admin work from Whatsapp, Slack, Telegram etc
-
I started freelancing at 15. By 20, I was running a 12-person Webflow studio doing 6 figures.
Then I lost €50K to clients who didn't pay. No contracts, just trust. The studio collapsed. I took on €40K in debt.
That experience stayed with me.
So I built Accordio... AI that writes contracts in 2 minutes, handles e-signatures, and processes payments with 0% commission.
Paste your meeting notes, AI extracts scope and terms, contract generates. Client signs, invoice auto-generates. One flow, no retyping.
Been vibe coding the times we all considered Gemini 2.5 pro as good as it gets. 4 complete rebuilds. Finally shipped something I'm not embarrassed by.
Just launched. Would love feedback from people who've dealt with the same payment nightmares.
3 Likes
3 Comments
3 Comments
-
1
You vibe coded Accordio through four rebuilds, and it now handles contracts, e-signatures, invoices, and payments. Who owns dependency and security updates behind it today, you, the AI tools, or someone technical?
-
2
Nice product, congrats on the launch. Curious what channels you’re currently using to get users?
-
1
Hey Ajayi... any channels that I can get my hands dirty in:
Mostly Linkedin worked great
Newsletters
AI tool listings
Cold outreach via DMs and personalized emails
Just started doing AEO with Surfer and... well, Indie Hackers :)
About
Lost €50K to clients who didn't pay. Web design studio almost collapsed. Built Accordio so freelancers can stop relying on trust and start getting paid.






6 Comments
The low-frequency contract problem is real, I had the same issue with client work where invoice #1 happened once and the only recurring job was the awkward follow-up after silence. I started with Stripe nudges and a sheet, now I'm building ChaseFlow just for that chase layer, lol the chat gateway angle makes sense if it can keep the full thread memory.
Love this pivot, Roma — turning dormant ops modules into a chat interface is a sharp execution move.
Whoa observation: did you see this week’s builder pattern where teams adding agent-to-agent verification before sending invoices cut follow-up confusion because each action is proven, not just automated?
If you’re experimenting with that workflow, would love your take on this live test: https://www.clawbarter.com
Great pivot story — turning a low-frequency contracts tool into a chat-first execution layer is a smart move. If you publish one concrete “request-to-cash” timeline (message sent → contract signed → payment cleared), it could make the value instantly obvious to new users. We’re currently testing autonomous agent-to-agent trading. Would you like to have your agent join a live test? https://www.clawbarter.com
The “admin work is dead” angle is strong — especially if you can show it in action. A quick before/after workflow demo could make this hit harder.
Working on exactly that. Planning a demo showing the full loop... client says "yes" in WhatsApp, contract gets generated, signed, invoice sent, payment tracked. All from one chat thread. The before was me chasing clients across 6 apps and still losing €50K. The after is one message.
That’s powerful. The “before vs after” framing is gold — especially the €50K story.
If you can visually show 6 apps → 1 chat thread, that’ll hit hard.
Would love to see the demo when it’s ready.