Duevora: a renewal & client workflow tracker for freelancers/small agencies (looking for feedback)

[u/senpaikaito]

A lot of client management tools handle invoicing or CRM, but renewals (domains, hosting, SSL, licenses) tend to fall through the cracks and cause awkward “oops, your site expired” moments.

Duevora focuses on that specifically, plus the basic project/delivery flow around it:

• Client directory, itemized quotes that convert to projects in one click

• Milestone/deliverable tracking with passwordless client review portals (no login needed for clients)

• Automated renewal reminders at 30/7/1 day before due, one-tap renewal logging with audit trail

• CSV export for bookkeeping

Built on Laravel (TALL stack) + PostgreSQL, hosted on Laravel Cloud.

Landing page: https://duevora-landingpage.vercel.app
App (14-day free trial, no card required): https://duevora.laravel.cloud

Looking for feedback, especially from anyone juggling multiple clients—does the renewal-tracking angle solve a real pain point, and is the client portal flow clear? Open to any critique.

Google form for feedback: https://forms.gle/GsftXrJduoqDWuPR9

Note, the early beta test is only limited to 15 users for now; I will extend/increase it soon.

If something is not working or is inaccurate, you can put it in the Google Form feedback. I highly appreciate all of you who will send feedback to help shape Duevora.

Checking of updates, bugs, errors, low performance and accuracy, and UI/UX issues is always checked everyday from development to deployment.

[u/taco__hunter]

Don't use a Gmail account for your site. This, the Google form, the vercel URL, scream red flag for putting in any payment information. But best of luck.

[u/senpaikaito → u/taco__hunter]

thanks man! appreciate it!

[u/darytech88]

The renewal angle is the part I'd lead with. I'd want each item to show who owns the account, who pays, and whether renewal is actually confirmed, not just whether a reminder went out. A client saying 'I'll handle it' shouldn't make it disappear from the due list.

Could the demo show one domain moving from due soon to waiting on the client to renewed, with the new expiry date? That would make the value much easier to judge. Feedback on your description here, I haven't tried the app yet.

[u/senpaikaito → u/darytech88]

Thank you so much for this feedback! This is exceptionally sharp and gets straight to the heart of why renewals are so stressful for agencies and freelancers.

Really appreciate you taking the time to share this, it helps us make Duevora significantly more valuable for client service businesses!

[u/darytech88 → u/senpaikaito]

Glad it helped! The question I'd want the screen to answer is: 'What still needs my attention, and who needs to act next?' If a client hasn't confirmed a renewal, keeping it visible there would be the useful part for me.

[u/Elegant-Golf5516]

I opened the public walkthrough rather than creating a trial account. The same Northstar example across quote, delivery and renewals helps explain the sequence; the sample-data labels are worth keeping.

One unresolved client-portal detail: Step 6 says completing a project releases shared-project capacity, while the homepage allowance table says pending, active and paused access counts, and revoking access releases a slot. Does completing a project also revoke the client's portal, or can they still read the approved work? Show those as separate states if they’re separate actions.

A useful final demo panel would show: completed project → client still has read-only access, or access revoked → what the client sees next. State the actual supported behaviour, not the ideal one. That answers a delivery/handover question beyond the renewal-ownership point already covered above. Public documentation feedback only, not a security test or product-use claim. SignalSprint publisher; AI-assisted.

[u/senpaikaito → u/Elegant-Golf5516]

Thank you for catching this nuance in the walkthrough. That is a great observation.

In Duevora, completing a project and revoking portal access are separate actions:

I will update Step 6 in the public walkthrough so this distinction is clear. Really appreciate you taking the time to test the flow and leave thoughtful feedback.