How can we build one internal request tool for sales, operations, and finance without creating another inbox nobody owns?

Question

Tyler Smith · Accepted Answer

Build around the handoff, not around a shared inbox. Every request needs a receiving owner, an explicit next action, and a clear definition of completion.

Cross-department tools often expose disagreements about the process. Sales may think a request is complete when it is submitted. Operations may need supporting details before work can start. Finance may need an approval before releasing funds. Resolve those expectations before generating screens.

Use the EOS approach of simplifying a complex process into its essential steps. Map one request type from submission through completion, then build only the information and decisions needed to move it forward.

Include:
- A short intake form with required information for that request type.
- A named receiving owner and a backup routing rule.
- Plain-language statuses that describe what happens next.
- A visible reason when a request is blocked or returned.
- A record of decisions and handoffs.
- Notifications for action or exceptions, rather than every minor update.

AI can help summarize a long request or suggest a category. Keep consequential routing rules explicit, and let people correct classifications. Do not let an uncertain AI guess silently send a sensitive request to the wrong department.

At Batteries Included, this is the kind of bounded internal workflow to build with Lovable or Replit: a usable process rather than another reporting layer.

Pair the launch with role-specific training using realistic examples. Measure completion time, returned requests, and unresolved handoffs. If employees still need a separate message to find out who owns the next step, fix the workflow before adding more features.