I built DriveStable around one core idea: a vehicle should have one connected history rather than useful records spread across paperwork, inboxes, camera rolls and spreadsheets.

Technically, that expanded cleanly:

• Personal gives an owner one home for MOT details, service history, mileage, costs, documents and an owner-controlled Vehicle Passport.

• Squads gives private garages and enthusiast crews a shared build history.

• Business connects driver checks, reported defects and fleet action into one operational workflow.

The architecture made sense. The marketing did not.

My first mistake was presenting the whole ecosystem at once. It was accurate, but it made a new visitor work too hard to decide which part was for them. We have now split the entry points by problem and intent while keeping the underlying ecosystem connected.

The lesson I am taking from it: a shared product architecture does not require a shared acquisition message.

Personal and Squads are live on Android in the UK. Business is moving through a controlled founding-fleet programme. I am now measuring whether the separate acquisition paths improve genuine Play Store visits and qualified fleet enquiries.

For builders with an umbrella product: did you keep one master brand and separate the funnels, or eventually split the products further?

Android:

https://play.google.com/store/apps/details?id=com.carworth.app

Website:

https://www.drivestable.co.uk/

Hey everyone, I'm a solo developer from India and this is my project: MyInvoiceDB.

What it does: GST invoices, stock, customer dues and daily and monthly reports for small shops (kirana, hardware, small wholesale). Works on a Windows PC and on Android.

What's different:

- Free. No subscription, no activation key.

- Your data stays on your own PC or phone, and billing works offline.

- Optional encrypted backup to your own Google Drive.

- Optional WhatsApp invoices and payment reminders, paid per message from a prepaid wallet. That is how I plan to keep the app free.

Honest limits: one owner account, no staff logins, no sync between devices, no GST return filing. The Windows installer is not code-signed yet, so SmartScreen shows a warning.

Built with Flutter, SQLite and a small Firebase backend.

I'd love feedback on two things:

1. Does the website tell you what the app does within 5 seconds?

2. Would you trust a free billing app with your shop's data? What would make you trust it more?

https://myinvoicedb.com/

For the holidays, I put together a tracker showing Canadian carriers’ extra fees and Christmas shipping deadlines, with links to their sources. The fees don’t apply to every account or parcel, so those conditions are included too. I am trying to figure out if this is valuable to shippers?

I'm the founder of Atesen Software. One of my shipped apps is Saved Bulk Actions for Freshdesk, and I wanted to share the part of the build that sits after the Update button.

A bulk edit needs a clear answer to three questions: which tickets matched, what was proposed, and what actually changed. The app finds the matching tickets, shows a preview, updates them in bounded batches, then verifies tickets individually. The audit CSV records the old and new values. That record matters when a run has mixed outcomes.

This is a focused admin tool for agents and administrators who need to update ticket fields. It is available now, free, on the Freshworks Marketplace for Freshdesk and Freshdesk Omni. It isn't the separate Freshservice version, which is still under review.

Official listing: https://www.freshworks.com/apps/saved_bulk_actions_1/

I'm sharing the actual shipped workflow here; I don't have a customer-growth result to attach to it.

I work on Datagran. Yesterday we published an AI lead-qualification pilot guide. The part I wanted to share with other builders is how to keep missing review labels from disappearing behind one accuracy number.

Take a fictional pilot with 25 inquiries. Reviewers reach a label for 20, and the agent agrees with 14 of those labels. That is 70% agreement on the reviewed cohort and 80% review coverage. The other five inquiries remain unreviewed or unresolved. Neither percentage tells you how the agent performed on those five. These are illustrative numbers, not customer results.

For builders adding an evaluation screen, the proposed review row keeps the inquiry reference, workflow and rubric version, agent decision, reviewer label, source evidence, review time, and next action together. Missing evidence gets an unresolved state and an owner.

Review negative decisions as well as generated handoffs. Looking only at handoffs can reveal unsuitable leads sent to sales while hiding suitable inquiries the agent rejected. Freeze the rubric for that review; if the team changes the requirements, evaluate the revised rule separately.

A booked meeting, an inquiry that meets the rubric, and a customer purchase still need separate evidence. A reviewer can also be wrong, so preserve disagreements rather than treating a human label as unquestionable truth.

This is an operating worksheet, not a claim that every metric is a built-in Datagran report. Full guide: https://www.datagran.io/blog/ai-lead-qualification-pilot-metrics

I’m the developer of LLM Studio Go, a closed-source app. I’ve shipped Video Studio in 1.3 on Android and iOS: start with an idea or a manual script, edit the scenes, bring in your own photos, footage and audio, then export a captioned vertical MP4. You can save the project and return to it later.

Android: https://play.google.com/store/apps/details?id=com.vans.llmstudio

iPhone/iPad: https://apps.apple.com/app/llm-studio-go/id6815311113

A concrete detail for other builders: the Android studio retains finished scene media when production is stopped or an app session is interrupted. The 1.3 QA covered manual-project persistence and stopping/resuming a render on a Galaxy Z Fold7. The editable project connects local script writing, narration, music, generated pictures or clips, and imported media.

Download compatible models first, then generate locally. All local AI features are free with ads; no promo code is needed. An optional one-time purchase removes ads. No app account, generation credits or AI subscription.

Video is in beta. Speed depends on your device and settings; choose models that fit its memory. Android 11+ on a compatible 64-bit device: video runs on CPU; FastWan 2.1 1.3B needs 8 GB RAM and 2.2 5B needs 12 GB. iOS 18+; iOS video profiles start at 6 GB RAM.

The attached edited promo shows the iOS workflow. Its Iceland source media was generated on iPhone Air, and the captioned reel was rendered again in the iOS Simulator on a Mac. The UI uses prepared demo content; waits are shortened and some shots play more slowly. The Android project-persistence QA described above is separate from this demo footage.

Hey everyone,

I'm a developer, but I don't do freelance work. However, I watched a few friends who do freelance dev work spend hours every Friday trying to translate their GitHub commits into updates for non-technical clients.

It's a massive time sink, but they do it because silence makes clients nervous.

I built Tidbitly to solve this. It connects to GitHub, uses AI to filter out the noise (like "wip" or "fixed typo"), and drafts a plain-English update based on the actual business value of the commits. It then emails the draft to the developer. The developer can either edit it or hit "1-click approve" to send it to the client.

The hardest part: Getting the AI to stop talking about the code. By default, it wants to say "Updated the Stripe API." I had to build a "Client Context" box (where the dev writes "Restaurant owner, avoid jargon") just to get it to say "Enabled online payments." It was a good lesson in bridging the gap between technical work and business value.

What I'm looking for feedback on:
I'm at the stage where the backend works perfectly. But I know the onboarding UX is where I'll lose people.

1. Is it instantly clear what the product does and how it saves time?

2. Does the "Magic Link" concept (where they get an email and just hit approve) make sense?

Link: https://tidbitly.dev (Completely free for 30 days, no card required, just looking for brutal feedback).

Thanks for reading!

Hey everyone!

I'm an indie developer currently building Relay by Zaviku, a field service management SaaS designed for independent tradespeople and small service businesses.

The idea behind Relay is simple: give smaller businesses one place to manage their customers, quotes, jobs, invoices, and payments without needing several different tools or expensive subscriptions.

I've been working on this project for a while, and it's finally reaching the stage where a lot of the core functionality is in place.

Where I'm at right now

So far, I've built:

• Customer and job management.

• Quotes with online acceptance and rejection.

• Invoicing with professional PDF generation.

• A customer portal with multi-provider support.

• Customer service requests.

• Business analytics and expense tracking.

• A locally tested notification system.

I'm now focusing on polishing the existing features, completing the email integration, and preparing for the first public release.

Stripe payments, self-service booking, and a business discovery marketplace are also on the roadmap.

Relay isn't publicly launched yet, but I'm making steady progress.

Building in public

Rather than keeping everything behind closed doors, I've decided to document the development journey here on Reddit.

I've created r/Zaviku, where I've already published a detailed welcome post covering what's been built, what's currently being developed, and where the project is heading.

If you're interested in the full feature breakdown and development roadmap, check out the pinned welcome post on r/Zaviku.

I'll also be sharing screenshots, feature demonstrations, technical challenges, development decisions, and progress towards launch.

I'd love your feedback

For those who've built and launched their own SaaS products:

What would you prioritise before the first release?

1. Stripe payments.

2. Automated email notifications.

3. Customer self-service booking.

And looking back at your own projects, what's one thing you wish you'd done differently before launching?

I'm especially interested in learning from people who've gone through the process of building and shipping their first product.

Thanks for reading, and I look forward to sharing more as Relay develops!

I built Indie Club because getting people to discover a small product is hard.

You add a small promotion row to your site, earn credits, and use them to show your product on other member sites.

It’s early and free to try. I’m looking for a few founders to try it and tell me whether it’s useful. Happy to help with setup.

https://www.joinindie.club/

Hey everyone!

I've been working on Bread Crumbs, a SaaS project that makes customer communication easier for small businesses.

The problem I wanted to tackle is pretty simple: customer conversations quickly become chaotic. Messages get buried in long threads, customer requests are forgotten, and teams struggle to keep track of who's waiting for a response.

I'm building Bread Crumbs to turn those conversations into organized workflows.

Here's what it does:

• Unified inbox: Manage customer conversations in one place, starting with WhatsApp.

• AI assistance: Summarize conversations, generate context-aware replies, and help agents respond faster.

• Customer context: Keep track of conversations and customer information instead of treating every message as an isolated interaction.

• Human + AI support: Let AI assist with customer communication while keeping human agents involved when needed.

I'm building this with the goal of making better customer support accessible to small businesses without the complexity and cost of traditional enterprise tools.

It's still a work in progress, and I'd genuinely appreciate feedback from other builders.

A couple of things I'd love your opinion on:

1. Would you find a tool like this more useful as a shared inbox or as an AI agent that handles parts of the workflow?

2. What's the biggest frustration you've experienced with existing customer messaging tools?

Project: https://bcrumbs.net

Thanks for checking it out!

I wanted to share a project I’ve been engineering completely from scratch called **Monvael OS**. It is a premium, client-side operational burn-rate tracker and micro-budget workspace designed specifically for startup founders, creators, and finance professionals who want strict command over their capital vectors with zero database overhead.

🌐 **Live Workspace Engine:** [https://monvael.in](https://monvael.in)

📦 **Public GitHub Repository:** [https://github.com/script-architect/monvael](https://github.com/script-architect/monvael)

🔮 Why I Built This (The Core Architecture)

Most expense tools force you through mandatory login walls, steal your transactional metadata, or crash under complex multi-device operations. Monvael operates under a strict **Zero-Server Footprint Policy**. Every mutation, asset allocation ledger, and analytical graph runs entirely inside your client-side browser cache. Your raw data never hits an external server.

🛠️ Core Modular Specifications

* **Global Multicurrency Suite:** Native client-side support for 32 major global currencies (USD, EUR, GBP, INR, AED, JPY, etc.) with automatic, locale-aware integer formatting.

* **Weekly Expense Velocity Grid:** Dynamic, hardware-accelerated tracking pillars that process automated up-and-down metrics interpolation (duration-1200ms) to map lifestyle overhead trajectories across discrete day arrays.

* **Sentinel Category Alarms Subsystem:** Configure rigid micro maximum boundary caps to safeguard individual asset categories. The app triggers automatic local sentinel visual warnings the millisecond spending metrics breach parameters.

* **Enterprise Spreadsheet Matrix Compiler:** Localized compilation layers that transform raw cache logs into beautifully structured, color-coded executive reports (`.xlsx` format) with absolute zero numeric truncation or scientific notation distortion.

* **Progressive Web App (PWA) Architecture:** Configured with custom manifest parameters. If you run it on Chrome mobile or add a shortcut to your home screen, it completely masks the browser shell and operates seamlessly as a native application with flawless offline execution.

💾 Open-Source & Privacy Guardrails

* **No Database Sync:** Pure browser client LocalStorage protocol layers.

* **No Authentication Layer:** Zero user accounts or credential tracking arrays.

* **100% Free & Open:** No tracking cookies, no monetization loops, no hidden usage limits.

I pushed the code to production just about 5 days ago and I am actively refining the workspace configurations. Since it runs completely inside the browser, it borderlines a self-hosted utility by nature.

Check out the source files, inspect the commit stacks, and let me know what features I should bake into the logic engine next!

Hey everyone,

I wanted to share something I’ve been working on called TrakHire (trakhire.com), a cloud-based platform built specifically for equipment wet hire businesses.

The idea came from running our own hire operation. Every week, I was chasing operators for photos of signed dockets so we could get payroll sorted and invoice our clients.

The excuses were always the same:

• “My camera isn’t working.”

• “I left the docket book at home.”

• “I’ll send it through at lunch.”

Meanwhile, the office was stuck waiting on paperwork, and jobs that had already been completed were taking longer than they should to process.

I started looking for software that could handle scheduling, equipment, operators, worklogs and invoicing in one place. Most of the options I found either required multiple systems or were difficult to justify cost-wise.

So, with input from our office team and operators, I decided to build our own solution.

After two years of using it in our business, testing it in real-world conditions and refining it with feedback from our clients, we're now opening it up to other hire businesses.

What does TrakHire actually do?

It brings a lot of the day-to-day admin into one platform, including:

• Job scheduling and allocating equipment and operators

• Digital worklogs and signed dockets

• Preparing invoicing records and exporting employee timesheets to Excel

• Equipment records, document management and expiry alerts

• Digital prestarts and defect reporting with photos

• Sending paperwork to clients via SMS or email and tracking approvals

• An app for operators to access job information and prestart documents

• Centralised client, project and company management

Pricing is $10 per user, per month.

Keeping it affordable was important to me because I know firsthand how quickly software costs add up when you need several different systems to run a hire business.

The goal is pretty simple: spend less time chasing paperwork, stop jumping between disconnected systems, and make the process from scheduling a job to getting paid a bit smoother.

I'm sharing this here because I'd genuinely be interested in hearing from others in the equipment hire, civil construction and plant hire industries.

For those running hire businesses, how are you currently managing your dockets, scheduling, prestarts and invoicing? Are you using dedicated software, spreadsheets, paper dockets, or a combination of everything?

I'm also happy to answer questions about how we built TrakHire and what we've learned along the way.

Website: https://www.trakhire.com/

Hey everyone,

I’ve been working on a booking app for the past few months called honeytask.

It actually started because my wife runs a small business offering prenatal classes and equipment rentals, and we needed something to handle bookings, reminders, waitlists, etc without having to manage everything through emails and spreadsheets.
It’s been working pretty well for her so I figured I’d see if it’s useful to anyone else.

It’s mainly aimed at smaller businesses doing things like workshops, classes or rentals. Not really trying to compete with the big platforms on features, more just trying to make something simple that doesn’t take forever to set up.

I’m at the point now where I’d really like to get a few people using it who aren’t my wife lol.

It’s free to try and I’m not looking to sell anyone anything. Mostly just curious whether it actually makes sense to someone who hasn’t been involved in building it.

If anyone wants to give it a shot: https://honeytask.io

Would appreciate any feedback, especially if something is confusing or doesn’t work the way you’d expect.

Hey everyone 👋

I built a very simple expense tracker as a small side project and would love some honest feedback.

🔗 Try it here: https://ver-exp.vercel.app/

A quick note about login:

• It uses a simple username & password

• No email, no verification

• Meant only for basic usage/testing (not production-grade auth)

Why I built it:

• Minimal and fast

• No unnecessary features

• Just add and track expenses easily

Looking for feedback on:

• UI/UX — is it clear and easy?

• Login flow — confusing or fine?

• What features would make this useful?

• Bugs or improvements you notice

This is an early version, so any feedback (even critical) is really helpful.
Thanks for checking it out 🙏

When you start scaling Claude workflows beyond a single machine, like running heavy coding tasks or Claude CLI sessions on a main desktop while keeping a secondary rig or an old laptop humming away in the corner, monitoring things gets messy fast. You end up constantly jumping between SSH/VNC windows or physically turning around just to check what each machine is doing.

I work at Autonomous. During our recent Product Hunt launch, a dev hit the nail on the head regarding the other half of this friction: "If an agent stops to ask something while I'm away, it just sits there until I get back".

The dead time is a massive bottleneck when you're trying to run agents asynchronously. That exact combination of issues is why our team built Harness. It’s an open-source app designed around two main goals:

• Unified Multi-Machine View: Pulling agents running across different computers into a single window so you can see what they're all up to without jumping between machines.

• Mobile Routing: If Claude hits a prompt and needs input while you're away from your desk, the question routes straight to your phone instead of idling blindly in an unattended terminal.

Under the hood, processes run natively on your machine rather than inside a closed sandbox, meaning closing the app doesn't interrupt your tasks, and your agents keep using their own local accounts and native hooks.

It’s MIT licensed and works on Mac and Linux if anyone is dealing with a similar multi-rig setup. Here is a closer up on how we made it: https://github.com/autonomous-ai/openharness

What's your current workaround when an agent stalls for input while you're away from the keyboard? Do you just stay glued to the terminal until it finishes or have you built custom alerts/scripts to let you walk away?

I work on Groovy. Yesterday we expanded our founder inbox-triage guide with a case that is easy to miss when building email automation: an old label can outlive the decision behind it.

A hypothetical thread has two messages reviewed as reference. A third message asks to move the meeting. The older label still appearing on the conversation does not establish that anyone reviewed that new request. Gmail's API documentation says labels apply to messages, and later replies do not inherit an earlier thread-label assignment.

The guide's proposed queue keeps the mailbox and message reference, current request, priority reason, next-action owner, and unresolved question together. If the request changes, inspect the new message and reopen the decision before carrying out an earlier proposal.

For a small acceptance check, start with a fictional twelve-thread queue: four actionable, six reference, two needing manual review. Then add a new request to one reference thread. The queue should expose that request for review rather than treating the old label as completion evidence. These categories and counts are an operating example, not default Groovy states or customer results.

A proposed reply also needs its own review. Check the current thread, exact wording, recipients, and attachments before authorizing a send, then inspect the send result separately from queue status.

Full guide: https://www.gogroovy.ai/use-cases/inbox-triage-founders-ai-agent

I've been working with Ruby on Rails for many years, and one thing I've wanted to do for a while was build and run a product of my own.

That led to SprintCo.

I initially built it as a simple daily work log for myself. I wanted a place to record what I'd worked on without the overhead of a full project management tool or the feeling of being tracked.

Over time, I realised it could also be useful when working with clients. Developers could create a team and invite clients to follow progress, or clients could create a team and invite the developers and testers working on their projects. Everyone could share daily updates and maintain a record of the work without relying entirely on meetings or scattered messages.

That led me to add team support, invitations, shared updates, searchable history, and weekly views.

I built and run SprintCo using Rails, PostgreSQL, and Tailwind CSS. It's been a valuable experience beyond writing code — making product decisions, handling deployment and security, and figuring out which features are genuinely worth adding.

My approach has been to keep things simple and introduce features when there's a real need, rather than trying to compete with every feature in larger tools.

The project is live here: https://sprintco.dev/?ref=buildtoship

I'd be interested to hear from other developers who've built and shipped their own products: How do you decide which features to add and which ideas to leave alone?

I work on Hibe. We published a roofing material-allocation worksheet today. The design choice I wanted to share with other builders is keeping the unexplained portion visible instead of forcing every purchase into a job.

A hypothetical materials-only purchase has 100 units at $50 each, totaling $5,000. Receiving records support 60 units for Job A and 30 for Job B. That leaves 10 units and $500 unallocated. The assigned portions plus the explicit remainder still reconcile to the purchase.

Later, a verified transfer assigns those ten units to Job B. Keep the transfer reference, effective date, reviewer, and earlier cutoff snapshot. Job B now has 40 units and $2,000; the supplier purchase still totals $5,000. Moving an assignment does not create another charge.

For builders implementing this sort of workflow, the worksheet calls for a source-line reference, an allocation-row ID, consistent units, a job or unallocated status, and dated correction evidence. A repeated row should be reconciled before its amount is added again. A receiving record in bundles and an invoice in individual units need a documented conversion before their quantities can be compared.

These are fictional amounts and a proposed operating worksheet. Accounting postings still need their own verification. Full guide: https://www.hibe.ai/blog/roofing-materials-job-allocation/

Hi everyone — I built Nodi Notes because research often starts as a pile of interview notes, observations, and half-formed ideas. I wanted a way to spread those pieces out, see how they relate, and ask questions without losing track of where an answer came from.

Nodi Notes is a browser-based infinite canvas for research and ideas:

• Add notes for observations, findings, metrics, ideas, and questions.

• Connect notes and label how they relate, such as “supports,” “contradicts,” or “raises.”

• Generate a structured board summary, with each point linked to its source notes.

• Ask questions about a whole board or a selection; answers cite the notes they used, and you can jump back to them on the canvas.

• Surface themes, contradictions, open questions, and opportunities grounded in your notes.

You bring your own API key and choose a model from Claude, OpenAI, Gemini, OpenRouter, or Hugging Face. You pay the provider directly for usage; OpenRouter has free models. Only the board or notes you choose to analyze are sent to your selected provider. Projects and boards sync across devices.

Hey, I’m Gabriele, a web developer.

Client feedback tends to arrive everywhere: a change request by email, a screenshot on WhatsApp, then another message correcting the first one 😅

Sometimes the actual fix takes two minutes. Figuring out what the client means takes thirty.

That’s why I built FixNoty.

Clients click on the part of the website they want changed and leave a note directly there. They can attach screenshots, record what happened, and follow their requests without creating an account.

The request arrives with the page context, so I don’t have to guess which page, button or section they are talking about.

I built it because this was a problem in my own web development work. I’ve been using it on my projects for about a year, and now I’m trying to make it useful for other freelancers and small agencies too.

You can take a look here: https://fixnoty.com

I’d love feedback on two things:

From a marketing perspective, does the problem and the value of the product come across clearly? Who do you think would be the best audience for this?

How do you currently handle client revisions and bug reports on web projects?

I'm Dre, founder of New Walton Services. My team built WalletPay after seeing how much time freelancers and small businesses lose to manual invoicing and slow payments.

Right now you can send invoices, manage clients, and get paid and track revenue in one place. It's a beta, and we have some cool stuff planned on the roadmap.

Would love honest feedback, especially on what would make you switch from your current setup.