u/FrequentBike8327

New developer joins. KT takes 2 weeks. Client asks how it works. You spend an hour digging. Every Single Time.

I’ve been working on a large health-tech platform for quite some time now. A big beast, really-patient flows, appointments, notifications, billing, RBAC, integrations... A lot to juggle across front end and back end.

And I repeatedly encountered the same exact scenarios:

- New developer joining: scheduled KT. Someone sits with them for a week or two trying to explain what's what, which api does which function, how flows connect, which environment variables are necessary, what's live production, what's dead code no one cleaned up. This ties up a senior engineer for two weeks.

- Client asking: how does X work? The only option is to do a deep dive into the code. Confirm if the feature flag is on. Is the notification actually sending, or does it only exist in the codebase? The expected 30 second answer is now a 1 hour investigation.

- Client wants to know their own product: they really shouldn't have to call us. "what happens when a patient misses an appointment" should result in an actual answer, in plain English. Not a ticket. Not a meeting. Just an answer.

I’ve been considering building something to solve this. Not another docs tool. Not a code search engine. Something that can:

- Read your entire project-front-end repo, back-end repo, config files, database schema.

- Comprehend the flows, not just files.

- Figure out what’s actually live (are the environment variables set? Is the feature flag on? Is this piece of code even reachable?).

- Allow new devs to ask "how does billing work?" and get a detailed walkthrough in minutes rather than days.

- Allow a client to ask "is our reminder system working?" and get a "yes/no" with the rationale in plain English.

- Provide live reports on demand: "show me all users who got a notification this week" as a CSV.

Essentially, a chatbot that actually knows your product. Not just the code-but the whole thing. Configured by you, so it understands what’s important.

I don't have a product. I'm trying to validate the idea first.

So my genuine question: is this something that happens to you? How bad is KT in your current project? Does your client often ask you to explain how their own software works? And are there any existing solutions out there that really help?

I'd love to hear about real experiences.

reddit.com
u/FrequentBike8327 — 11 days ago

New developer joins. KT takes 2 weeks. Client asks how it works. You spend an hour digging. Every Single Time.

I've been working on a large healthcare platform for a while now. Complex stuff — patient flows, appointment systems, notifications, billing, role-based access, integrations. Lots of moving parts across frontend and backend.

And I kept running into the same situations over and over:

When a new developer joins — we schedule KT sessions. They sit with someone for 1–2 weeks just trying to understand what does what, which API does what, how the flows connect, what env variables matter, what's actually live in production vs what's dead code that nobody removed. Two weeks of a senior dev's time, gone.

When a client asks "how does this work?" — someone has to go digging. Trace the code. Check if that feature flag is actually on. Figure out if the notification actually sends or just exists in the codebase. What should be a 30-second answer becomes a 1-hour investigation.

When a client wants to understand their own product — they shouldn't need to call us. They should be able to ask "what happens when a patient misses an appointment?" and get a real, plain-English answer. Not a ticket. Not a meeting. An answer.

I've been thinking about building something for this. Not another documentation tool. Not a code search. Something that:

Reads your entire project — frontend repo, backend repo, config files, database schema

Understands the flows, not just the files

  • Knows what actually runs in production (are the env vars set? is the flag on? is this code path even reachable?)
  • Lets a new dev ask "how does billing work?" and get a proper walkthrough in minutes, not days
  • Lets a client ask "is our reminder system actually working?" and get a plain English yes/no with context
  • Can pull live reports on demand — "show me all users who received a notification this week" as a CSV

Basically: a chat interface that actually understands your project. Not just the code — the whole thing. Configured by you, so it knows what matters.

I don't have a product yet. I'm validating first.

So honest question — does this happen to you? How bad is KT on your projects? Does your client ever ask you to explain how their own software works? And is there anything that actually helps right now?

Would love to hear real experiences.

reddit.com
u/FrequentBike8327 — 11 days ago

Starting a WhatsApp-based micro-business seems easy until you're trying to handle 50-100 orders daily.

You lose confirmations because you get three messages at once. Your customers type “I want to order” and vanish. The addresses aren’t right. COD orders are returned because there was no partial advance collection. Also, you have no clue if a new customer will ghost you after receiving an order.

The sneaky RTO silently takes a bite out of your margin, and many WhatsApp sellers only start tracking it when the losses are already there.

This happened to me, and that’s why I’ve created Trustship (https://trustship.site).

It’s not a CRM, not a fancy dashboard – just an ultra-light solution that allows you to make orders, track their life cycle from order placement till delivery, run simple RTO calculations, and calculate a trust score for each of your customers based on his/her order history, so you would be able to predict if the order will be risky.

It’s just started and I am building it up. If you are a seller like me, I’d prefer your critical feedback to those silly five-star reviews.

Try. Let me know what’s wrong. Early users get lifetime access.

reddit.com
u/FrequentBike8327 — 12 days ago

Running a small business on WhatsApp sounds simple until you're juggling 50–100 orders a day.

I was managing 60–70 orders a day through WhatsApp last year. Seemed fine at first.

Then I started missing confirmations because three chats came in simultaneously. Customers would say "yes I want it" and I'd ship — only to get it returned because the address was wrong, or they'd simply changed their mind. COD returns were the worst. No advance collected, courier charges eaten, product back in damaged packaging.

The thing that really got me was I had no way to know which customers were repeat problems. Every new order felt like a gamble.

I looked for something simple to handle this — just order tracking, a basic customer trust score, RTO flags before shipping. Everything I found was either too complex or built for large operations.

So I spent a few months building something myself. Nothing fancy — you create orders manually, track status, it flags risky orders based on past customer behavior, reminds you to collect advances on COD.

Still very rough. I use it myself daily which is the only reason it works at all.

If anyone's dealing with similar stuff, happy to share what I built. Would genuinely value feedback from people who actually run WhatsApp-based businesses over people who just test things and leave.

reddit.com
u/FrequentBike8327 — 12 days ago

Running a small business on WhatsApp sounds simple until you're juggling 50–100 orders a day.

You miss confirmations when three chats come in at once. Customers say "I want to order" and disappear. Addresses are wrong. COD orders return because nobody collected a partial advance. And you have zero way of knowing if a new customer is likely to ghost after delivery.

RTO (Return to Origin) quietly eats your margins, and most WhatsApp sellers don't even track it until the damage is done.

I faced the same mess, so I built something to fix it: Trustship (https://trustship.site).

Not a CRM. Not a complex dashboard. Just a dead-simple way to create orders, track them from placed to delivered, run basic RTO checks, and build a trust score for each customer based on their order history, so you know before you ship whether the order is risky.

It's early and I'm still building. If you're a seller dealing with this, I'd rather have your honest feedback than fake five-star reviews.

Use it**.** Tell me what's broken**.** Early users get lifetime access, no catch.

reddit.com
u/FrequentBike8327 — 12 days ago

Running a small business on WhatsApp sounds simple until you're juggling 50–100 orders a day.

You miss confirmations when three chats come in at once. Customers say "I want to order" and disappear. Addresses are wrong. COD orders return because nobody collected a partial advance. And you have zero way of knowing if a new customer is likely to ghost after delivery.

RTO (Return to Origin) quietly eats your margins — and most WhatsApp sellers don't even track it until the damage is done.

I faced the same mess, so I built something to fix it: Trustship (https://trustship.site)

Not a CRM. Not a complex dashboard. Just a dead-simple way to create orders, track them from placed to delivered, run basic RTO checks, and build a trust score for each customer based on their order history — so you know before you ship whether the order is risky.

It's early and I'm still building. If you're a seller dealing with this, I'd rather have your honest feedback than fake five-star reviews.

Sign up free. Use it. Tell me what's broken. Early users get lifetime access — no catch.

reddit.com
u/FrequentBike8327 — 12 days ago

Anyone here selling on WhatsApp and tired of returns eating your profits?

I am building TrustShip (https://trustship.site) to fix exactly that. It's for small sellers who run their business through WhatsApp chats. Buyers send messy messages and half the orders end up as returns because the address was wrong or the buyer changed their mind.

Here's what it does: it connects to your WhatsApp Business number, reads the messy chat, and turns it into a clean order automatically. It verifies the buyer's phone number, checks if the address is real and deliverable, and sends a quick WhatsApp confirmation before you ship. It also flags buyers who usually refuse deliveries, shows only verified orders in a clean dashboard, and works with any courier you already use.

Not fully done yet, still waiting on WhatsApp Business API approval and finishing some parts. Should be ready next week. Early users can sign up free right now.

If you sell on WhatsApp or know someone who does, I'd love your honest take. Does this actually solve a real pain, or am I missing something?

reddit.com
u/FrequentBike8327 — 15 days ago

Anyone here selling on WhatsApp and tired of returns eating your profits?

I am building TrustShip (https://trustship.site) to fix exactly that. It's for small sellers who run their business through WhatsApp chats. Buyers send messy messages and half the orders end up as returns because the address was wrong or the buyer changed their mind.

Here's what it does: it connects to your WhatsApp Business number, reads the messy chat, and turns it into a clean order automatically. It verifies the buyer's phone number, checks if the address is real and deliverable, and sends a quick WhatsApp confirmation before you ship. It also flags buyers who usually refuse deliveries, shows only verified orders in a clean dashboard, and works with any courier you already use.

Not fully done yet, still waiting on WhatsApp Business API approval and finishing some parts. Should be ready next week. Early users can sign up free right now.

If you sell on WhatsApp or know someone who does, I'd love your honest take. Does this actually solve a real pain, or am I missing something?

reddit.com
u/FrequentBike8327 — 15 days ago