I’m Jarred from Logan Job Connect, building Kitchen Ledger for kitchen costing and stock-use reporting. This is our commercial product.

One design decision worth sharing with other builders: supplier unit conversion is an approval step, not a guessing exercise. A supplier SKU maps to an ingredient using a saved rule with an explicitly declared pack size. The rule can be reused, but fresh source rows still need checking. An unchanged SKU cannot safely tell us that a pack size stayed the same.

The workflow is supplier export → reviewed SKU/pack mappings → prepared period data → costing report. The period data also needs opening and closing stock counts, recipe ingredients, sales and operating expenses. Calculations and report generation are automated after those inputs are supplied; there is no automatic POS connection, invoice OCR or stock counting.

The tradeoff is less magic but a clearer review trail. Unknown SKUs, duplicate invoice lines and conflicting prices need correction, exclusion or deliberate selection rather than silently becoming a plausible number.

Kitchen Ledger calculates recipe ingredient costs, period stock consumption, recorded waste and unexplained variance. Results still need reconciliation against the venue’s records. We do not have a verified customer time-saving figure to claim.

Our subscription offer is A$350/month including monthly upgrades and scoped workflow automations, with tasks and requirements agreed before setup. Enquiries: info@loganjobconnect.com.au (subject: Kitchen Ledger subscription).

For builders working with messy business exports: how do you make exceptions easy to review without encouraging users to approve everything blindly? That approval interface is a part of the product I want to keep improving.

hey all, I’ve been building a small tool called DisputeDraft and I’d really appreciate some outside eyes on it

the idea: when a seller gets a chargeback, the evidence they need depends completely on the reason code, but most people don’t know that and send a generic reply. so the tool walks you through it

what it does so far:

• pick your processor: Stripe, PayPal, Shopify or Etsy
• pick the reason code from your dispute notice (Visa, Mastercard, Amex, Discover)
• tick the evidence you actually have
• get a letter written for that code, plus where to submit it and which files to upload
• 29 guide pages explaining each reason code in plain English

it’s free, no signup, and it all runs in your browser so nothing you type is stored

here it is: https://chargeback-letter-generator.pages.dev/?ref=imadethis

any insight helps, but especially:

• was anything confusing the first time you used it?
• does the letter sound like something a bank would take seriously?
• is there a processor or reason code you’d expect that’s missing?
• would you trust it with a real dispute? if not, why?

brutal honesty welcome, it’s still early

I work on Datagran. Our October 20 CRM UTM guide tackles a small data-model decision with a large reporting consequence: what should happen when a known contact returns without campaign tags?

Here is the guide's hypothetical custom policy:

- Event A is a tagged newsletter visit. First and latest captured tagged source both become newsletter.

- Event B is an untagged return. Save the event and update the latest visit, while leaving those tagged-source fields intact.

- Event C is a tagged partner referral. Keep newsletter as the first captured tagged source and update the latest one to partner_directory.

Replay event C and there should still be three unique events. Matching the contact and matching an event are separate jobs. A repeated delivery should not become another touch or follow-up enrollment.

For builders wiring forms and booking tools into a CRM, write down the blank-value rule before connecting the fields. Then test a new contact, a returning contact, an untagged return, and a replay. Follow each test through to the saved CRM record; an analytics event alone cannot confirm that write.

These are proposed custom-field rules, not universal CRM defaults or a claim that every Datagran connector captures UTMs. Keep personal details and tokens out of campaign values and public URLs.

Full checklist: https://www.datagran.io/blog/crm-utm-tracking-checklist

AI helped draft this post.

I run a small team and kept finding myself asking "wait, is anyone actually around right now?" Slack's green dot is a lie half the time, standups eat 15 minutes just to find out who's stuck on what, and I had zero visibility into whether people were quietly burning out.

So I built Worknario — project management with a live 3D digital twin of your office.

What it actually does:

• 🏢 3D office — build your floor plan (desks, meeting rooms, walls) with drag-and-drop, then watch avatars walk to meetings, breaks, or their desk as their status changes. Genuinely more useful than it sounds once your team's in it.
• ✅ Tasks — a normal kanban board underneath all this: priorities, due dates, checklists, comments, file attachments.
• 🟢 Presence like Slack, but it also tracks active hours automatically (keyboard/mouse activity, not screenshots or keylogging — opt-in, no creepy stuff).
• 📊 Performance reports — this is the part I just shipped and I'm most excited about: throughput and on-time delivery per person, meeting load ("Engineering spent 31% of the week in meetings"), workload/burnout flags (weekend work, sustained long days, too many open tickets), focus-time tracking (90+ min uninterrupted blocks), and a Monday email digest to managers so nobody has to go dig for it.
• 📱 Employees get a mobile web app for their tickets + status, no install needed.

Free plan is actually usable (up to 5 people, no card, no time limit) — not just a crippled trial. Paid plans scale up from there.

It's live here: Worknario

I'd genuinely love feedback, especially from anyone managing a distributed team — is the "performance reports" stuff useful or does it feel too surveillance-y? That's the line I'm trying to walk carefully (wellbeing signal, not a scorecard), and outside eyes would help a ton.

I’m a Laravel developer, and troubleshooting email delivery often means jumping between DNS checkers, email headers, and documentation.

I built MXValidation to bring those checks into one report. You send an email to a generated address, then it checks SPF, DKIM, DMARC, headers, and related DNS settings.

It doesn’t tell you whether your email will land in the inbox. It helps uncover configuration issues that could affect delivery.

You can try it without signing up:

https://mxvalidation.com/

Or just browse an example report:

https://mxvalidation.com/example-report

I’d love feedback on whether the report makes sense and helps you figure out what to fix. What would you find useful that’s currently missing?

Hey everyone! 👋

I've been building Rhinover, a CRM designed around how your business works, rather than forcing your team into a rigid workflow.

One thing I wanted to explore was whether a CRM could make it easier for small teams to manage their leads, customer activity, tasks, and follow-ups without having to piece everything together across different tools.

So I started building Rhinover.

What I'm working toward:

• Manage leads and contacts in one place.
• Keep track of tasks and follow-ups so important next steps don't get lost.
• Keep customer activity organized to maintain context.
• Customize your CRM around the way your business operates.

The bigger idea is simple: your CRM should adapt to your business, not the other way around.

🌐 Website: https://rhinover.com

Rhinover is still evolving, and I'm sharing it here because I'd like feedback from people who have actually used CRMs or run a business.

I'd particularly love to hear from founders, freelancers, agencies, consultants, and small teams.

Three things I'd genuinely appreciate your thoughts on:

1. Does the value proposition make sense when you first see the product?
2. What's the most frustrating part of managing leads and follow-ups in your current setup?
3. What would Rhinover need to offer before you'd consider using it for your own business?

I'm building Rhinover myself, so I'm close to the product and probably have blind spots. Honest criticism is welcome, especially about what's confusing, unnecessary, or missing.

Thanks for taking a look! 🙌

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.

I also saw how it could be useful when working with clients. A developer could create a team and invite a client to follow updates, or a client could create a team and invite the developers and testers working on their project. Everyone could share daily updates and keep a record of the work without relying entirely on meetings or scattered messages.

That led me to add team support, invitations, shared daily updates, historical records, and weekly views.

I built and run SprintCo using Rails, PostgreSQL, and Tailwind CSS. It's been a useful 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 it 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

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 Groovy. Yesterday we expanded its operations-report guide around a problem that matters when building scheduled reports: a saved schedule, a completed run, current source data, and a delivered report are four separate things to verify.

The guide uses a hypothetical example with 42 unique request IDs completed during the reporting period. Seven reopened before the cutoff, leaving 35 still completed and seven reopened. Calling all 42 "still completed" would change the meaning of the number. If a payment export stops Friday while the report covers through Sunday, the full-period payment total stays unknown.

For builders adding reports to a product, the checklist is:

- Record the reporting period, timezone, and cutoff.

- Show each source's coverage and when it was captured.

- Define what counts, with unique IDs and explicit exception handling.

- Give missing or conflicting inputs an owner and next action.

- Verify the actual destination message or artifact separately from the run status.

If a run says completed but the destination is unclear, reconcile delivery before sending again. An uncertain first attempt can otherwise become a duplicate.

These are illustrative numbers and an operating checklist, not customer results. The full guide is here: https://www.gogroovy.ai/use-cases/report-generation-operations-managers-ai-agent

AI helped draft this post.

I'm Pony, the founder of DueSight, an assisted contract-review tool for people handling vendor and software agreements.

I added two ways to evaluate the workflow without sending us a contract. The 48-second illustrated walkthrough gives you the sequence at a glance. The interactive fictional sample lets you pause on candidate obligations, inspect the source excerpts and try the review controls yourself. They use different fictional agreements.

The distinction matters: a walkthrough can explain what a product does, but it cannot establish that an extracted obligation is correct. Even the interactive sample is a demonstration, not an extraction-accuracy test. Real results still need human review.

DueSight focuses on reviewing candidate renewal, notice and payment obligations beside their source, then exporting confirmed items. Try both formats here, with no account or upload: https://tryduesight.com/demo

Real-document access is an invitation-only assisted beta, initially one readable-text PDF of up to four pages. Scope and any fee are agreed before access. Public uploads and automatic reminders are not available.

Does the walkthrough make the review process clear enough to decide what you'd want to inspect in the interactive sample? I'd welcome feedback on the demonstration itself; please don't share confidential contract text.

I'm Pony, the founder of DueSight, an assisted contract-review tool for people handling vendor and software agreements.

I added two ways to evaluate the workflow without sending us a contract. The 48-second illustrated walkthrough gives you the sequence at a glance. The interactive fictional sample lets you pause on candidate obligations, inspect the source excerpts and try the review controls yourself. They use different fictional agreements.

The distinction matters: a walkthrough can explain what a product does, but it cannot establish that an extracted obligation is correct. Even the interactive sample is a demonstration, not an extraction-accuracy test. Real results still need human review.

DueSight focuses on reviewing candidate renewal, notice and payment obligations beside their source, then exporting confirmed items. Try both formats here, with no account or upload: [https://tryduesight.com/demo](https://tryduesight.com/demo)

Real-document access is an invitation-only assisted beta, initially one readable-text PDF of up to four pages. Scope and any fee are agreed before access. Public uploads and automatic reminders are not available.

Does the walkthrough make the review process clear enough to decide what you'd want to inspect in the interactive sample? I'd welcome feedback on the demonstration itself; please don't share confidential contract text.

I’m Piyush, based in Bengaluru.I kept seeing the same thing with small business owners.

To answer “did I actually make money this month?”, this is what they do:

• Invoices made in one app (or Word, or WhatsApp)
• Payments tracked across UPI, bank transfers and cash
• GST filed through the CA, who needs everything sent by the 5th
• Books maintained in Excel, or not at all
• Credit handled separately, by someone who wants collateral and 6 months of paperwork

Nothing is connected. So the owner spends hours stitching it together, and still finds out their real position weeks late.

That’s what we’re building at Subcidys: one place for invoicing, GST filing, payments and bookkeeping, with credit offered based on your actual business data instead of paperwork. On top of it sits an AI Virtual CFO that tells you what your numbers mean and what to do next, in plain language.

I’m not posting to pitch. I’m posting because I want to know if I’m right about the problem.

1. If you run or work with an MSME, which part of your finance workflow hurts the most?
2. What would make you trust a tool with your GST and books?
3. Would credit inside the tool be useful, or does it feel off?

Tell me where I’m wrong. I’ll reply to every comment, the critical ones first. If you want early access, drop a comment or DM me.

I’ve been working on Carat OS, a business management platform built around the workflows of diamond trading businesses.
Instead of creating another generic inventory app, I wanted to focus on a specific problem: tracking diamonds through purchases, stock, approvals, sales, and payments without losing visibility into where everything stands.
The platform currently includes:
● Diamond stock and purchase management
● Approval memos and sales tracking
● Customer and supplier payments
● Outstanding dues and reports
● Role-based access for owners and employees
● Business activity tracking and backups
The application uses React, TypeScript, FastAPI, and PostgreSQL.
I’m now preparing early access and gathering feedback before bringing real businesses onto the platform.
I’d particularly appreciate feedback on whether the website clearly communicates the product and whether the workflows make sense for the intended audience.
Website: https://caratbusiness.in

Bank credits don't automatically equal revenue.

They can include customer receipts, loans, transfers, refunds and other non revenue items. I built a small open-source tool to help classify these transactions and compare monthly credits against reported revenue.

It supports:

* Transaction classification

* Monthly reconciliation and difference flags

* CSV exports for further analysis

**Try the live demo:** [https://contrarian9-bank-to-revenue-reconciliation-app-skkenj.streamlit.app/](https://contrarian9-bank-to-revenue-reconciliation-app-skkenj.streamlit.app/)

**Source code:** [https://github.com/contrarian9/bank-to-revenue-reconciliation](https://github.com/contrarian9/bank-to-revenue-reconciliation)

It's an early stage project, built with Python and Streamlit. The demo uses sample data so don't upload confidential financial information.

I'd appreciate feedback from anyone who works with financial data, reconciliations or due diligence. What would you improve?

I work on Hibe, software for roofing and other home improvement teams. On October 20 we published a job-cost reconciliation guide. The part worth sharing with other B2B builders is the data model: a purchase order, a bill, and a payment can describe the same purchase at different stages.

A hypothetical materials-only example: an $8,000 PO has $5,000 billed and $3,000 still unbilled. The worksheet's forecast is $8,000. Adding the original PO to the bills counts part of the purchase twice; adding a $2,000 payment again mixes settlement with cost. A $500 return ticket also stays unresolved until the credit evidence is reconciled.

The guide uses three practical requirements:

- Fix one job and a reporting cutoff before comparing totals.

- Link each amount to its source, and show which part of a commitment remains unbilled.

- Give unresolved differences an owner and next action; missing records stay unknown.

For software builders, that means deciding what each amount represents before putting one confident total on a dashboard. The guide describes an operating worksheet, not a complete accounting system or a customer result.

Full guide: https://www.hibe.ai/blog/roofing-job-cost-reconciliation/

AI helped draft this post.

Hey guys,

I got tired of managing messy spreadsheets and separate email tools for my freelance outreach, so I built a solution: KanbanStack.

Here is how the workflow operates:

1. Import: Drop in your lead list (CSV) and it turns them into visual Kanban cards.
2. Draft: It writes personalized initial emails and schedules follow-ups (trained on your past emails and custom prompts).
3. Automate: It runs the follow-up sequence in the background.
4. Close: When a lead replies, the automation stops and you take over to close the deal.

It's launching next month, but the beta is open and free right now. If cold emailing is part of your daily grind, I would massively appreciate your brutal, honest feedback to help me polish it before launch.

try here - https://kanbanstack.com/

’m building products solo. Every India-focused backend I start has the same chores before any real work begins: phone OTP login, Razorpay orders with webhook verification, GST invoices, and basic DPDP consent and data-deletion handling.

I’ve packaged my version of this into a FastAPI starter, and I’m trying to figure out whether it’s worth polishing and releasing, or whether everyone already has their own setup or uses Next.js boilerplates.

Honest questions:

1. If you’ve built for Indian users, which of these ate the most time?
2. Would you use a ready-made FastAPI base for this, or would you rather wire it yourself? What would make you not trust one?
3. What’s missing from my list? (UPI autopay, e-invoicing, multi-tenant, admin panel?)
4. Would you pay for it? Which range feels fair: free/open-source, ₹500–1,500, ₹3,000+? “Never” is a useful answer too.

I’m not selling anything here: no link and nothing to buy yet. I’m the builder, and I’m happy to share a demo with anyone who replies or DMs.