Is document approval status tracking too narrow for a B2B SaaS?
I’m building a small B2B SaaS and I’m trying to validate whether the problem is real enough or too niche.
The problem:
Many companies already have places where documents live:
Google Docs, SharePoint, Dropbox, email attachments, internal storage, etc.
But the actual approval status often lives somewhere else:
- a spreadsheet
- email threads
- Slack / Teams messages
- meeting notes
- one person’s memory
Example:
A contract, proposal, SOP, vendor document, or client deliverable is waiting for approval.
The team needs to know:
- what is the current status?
- who or which side is it waiting on?
- why is it waiting?
- when was it last confirmed?
- what changed before?
But instead of checking one place, people ask in chat or email again and again.
I’m not trying to build a full workflow engine.
And I don’t want to build another task manager.
The product idea is more like a lightweight status layer for documents:
- current state
- responsible side
- waiting reason
- last confirmed update
- simple history
- read-only status page for stakeholders
The opinionated part:
I’m intentionally avoiding deadlines, overdue warnings, SLA logic, and performance tracking at the core level.
The goal is not to add pressure.
The goal is to reduce repeated status questions.
My question:
Does this sound like a real B2B pain worth building around?
Or is it too narrow / too easily solved with spreadsheets, SharePoint, Airtable, Smartsheet, or project management tools?
I’d especially like to hear from people who have seen this in consulting, logistics, sales ops, legal, procurement, client delivery, or internal operations.
I don’t think the pain is fake. I think the risk is positioning it too generally as “document approval status tracking.”
That can sound narrow or spreadsheet-replaceable.
The sharper wedge is probably around situations where document status creates repeated internal or client-facing interruption: contracts, proposals, vendor docs, client deliverables, compliance docs.
The buyer is not paying because they need another status field. They are paying because people keep asking “where is this stuck?” and nobody trusts the answer.
That is the angle I’d pressure-test first.
If useful, I can put the tighter version in writing: which buyer segment I’d test first, what pain message I’d lead with, and how I’d validate whether this is worth building before it turns into another workflow tool.
This is a very useful distinction.
I think you’re right that “document approval status tracking” sounds too generic, and maybe too easy to dismiss as “just use a spreadsheet.”
The repeated interruption angle feels sharper:
That is probably closer to the real pain I’m trying to understand.
I’d definitely be interested in the tighter version if you’re willing to share it — especially which buyer segment you’d test first and what message you’d lead with.
Yes, that’s exactly the layer I’d look at.
The important thing is not just “who approves documents.” It’s where unclear approval status creates repeated interruption, client anxiety, or internal accountability problems.
That difference matters because one sounds like a workflow feature, the other sounds like a real operational pain.
Drop your email and I’ll send over a tighter version. I’d keep it focused on the first buyer segment, the pain message to test, and how to validate whether LunaDocu is solving a painful enough problem before you build too broadly.
That makes sense.
The distinction between “workflow feature” and “operational pain” is probably exactly what I need to sharpen.
I’d definitely like to see your tighter version.
I’m still very early and mostly validating the problem myself, so I’m not looking for paid positioning help right now — but I’d really appreciate the high-level version if you’re willing to share it.
You can send it to [email protected]
Totally fair.
At this stage, I’d keep it very simple: don’t validate “document approval tracking.” Validate whether people are already losing time, trust, or client confidence because nobody knows where a document is stuck.
That’s the difference between a nice workflow feature and a real buying pain.
I’ll hold off on the deeper version for now since that would need more context and would be more useful once you have a few validation calls or patterns from real users.
Good luck with LunaDocu. If the feedback starts getting noisy and you want to turn it into a sharper buyer segment/message later, happy to revisit.
That’s fair, and this is already very useful.
The “time, trust, or client confidence” framing is much sharper than validating the tracker itself.
I’ll use that as the filter for the next step: find people who already have repeated document-status interruptions, not just people who think approval tracking sounds useful.
Thanks — this helped clarify the validation target.