One thing that keeps coming up from agency owners I talk to: agreements get signed with vague language ("unlimited revisions," open-ended scope), and it comes back to bite them 2 months later as a payment dispute or scope creep.
I'm exploring having Rixio's AI flag that kind of risky wording before you send an agreement and optionally draft a first version from your proposal notes instead of starting from a blank page.
Curious for anyone running an agency or freelancing solo: is this a real pain for you, or do you have it handled already (templates, a lawyer, gut instinct)? What would actually make you trust an AI-drafted clause enough to send it to a client?
honestly this looks solid, the time locked chat part is clever. one thing though, can you add a way to send the proposal straight from whatsapp when a client first messages you? like capture the chat context and turn it into a draft proposal automatically. would save so much copy pasting back and forth
@saniyetfjq Thank you Saniye!!
Really appreciate that, the time-locked chat took a lot of back and forth to get right so it means a lot that it's landing well
And yeah the WhatsApp idea is really smart honestly; I didn't think of that angle.
Capturing that first message and turning it into a draft proposal automatically would save people SO much back and forth, you're right
I'll keep it as a draft that pops up for you to review before it sends, not fully auto — I don't want pricing or scope stuff going out without a second look. But yeah adding this to the list, thanks for the idea 🙏
btw if you want to actually try it out I'd love to get you in and hear what else you run into — feedback like this is exactly what shapes what gets built next 🙂
Would love to see a built-in client onboarding flow where you can send a branded welcome packet with intake questions attached, so new clients are filling out their brief while you're still finishing the proposal.
@lyas1068058 Thank you İlyas!!
That's a really good one actually
A branded welcome packet with intake questions built in, so the client's already filling out their brief while you're wrapping up the proposal that's such a smart way to save time on both ends instead of doing it all sequentially. definitely see the appeal there
Right now the proposal just has the project name, so this would take it a step further. Adding it to the list for sure.
if you want to poke around the app I'd love to hear your take once you've used it, this kind of feedback is exactly what's shaping what comes next 🙂
honestly this looks really useful for freelancers juggling all that chaos. one thing that would make it a no-brainer for me is adding a built-in client portal view, basically a read-only link clients can open to see proposals, phase progress, and invoices without needing to log in or download anything. would save so much back and forth over email
@huriye413761
Hey Huriye, thank you for this — and honestly, you just described a feature we already built for exactly this reason 😊
We call them Guest Links. You generate a link per project, no signup or account needed on the client's end, and they can open it and see the scope, phases, agreements, and payment status — all read-only unless you specifically give them approve rights. If you want them to be able to sign off on a change order without creating an account, that's a toggle too.
We built this after seeing the exact pain you're describing: the constant back-and-forth over email just to answer "where are we on this?" or "did you get my last message?" Now that's just a link you drop into an email once, and it's always current — no PDF exports that go stale the moment something changes.
There's also a one-click export (HTML or CSV) from that same guest view, so if a client wants a record for their own files — say, for an invoice or their own bookkeeping — they can pull it themselves without pinging you.
I'd genuinely love for you to try it and tell me if it matches what you had in mind, or if there's a gap between what we built and what you actually pictured — sometimes the difference between "read-only link" as a concept and "read-only link" as something that actually removes email back-and-forth in practice is in the details, and real feedback from someone who's lived the chaos is worth more than anything I can guess at my desk. Would you be up for a quick look and letting me know what's missing?
Congrats on the launch, this looks genuinely useful for solo freelancers like me. One thing I'd love to see is a built-in client onboarding questionnaire that auto-fills the proposal fields based on the answers, so I don't have to copy paste info back and forth when a new lead comes in.
@gkeksawrsi Thank you, really appreciate that 🙏
Good news: the core of this already exists — it's called a Proposal Request Link. You generate one from your dashboard and send it to a new lead instead of a generic "tell me about your project" email. They fill a short guided form (client info → project idea → suggested terms → notes), and once you approve it, that submission becomes the proposal and auto-creates the project — no retyping their answers into anything.
What you're describing is a smart refinement of that, though — right now it's one flow (questionnaire → proposal), but it sounds like you want it to feel more like a proper intake questionnaire that's clearly separated from the proposal doc itself, so you can review and massage the answers before they turn into client-facing terms. That's a fair distinction, and it's the kind of nuance that's easy to miss until someone who actually runs new-lead intake every week points it out.
Two things I'd love your take on, if you don't mind:
Have you tried the current proposal link flow yet, or is this from picturing your usual process? Curious if it's close to what you need or missing something structural.
When you say "auto-fills proposal fields" — do you mean the questionnaire answers should populate an editable draft you can tweak before sending terms back, rather than becoming the proposal directly? That's a meaningfully different (and honestly, probably better) flow, and I want to build the right one, not just a version of it.
Really glad you flagged this — this is exactly the kind of gap between "technically solves it" and "actually removes friction" that's worth getting right before more people hit it.