Internal Sales Request Workflow MVP
A two-week internal MVP focused on clarifying and accelerating the sales-to-delivery handoff
Context & Problem
Sales teams were submitting project requests with inconsistent structure and varying levels of detail. This led to repeated clarification cycles, misalignment between sales and delivery teams, and unnecessary delays before work could begin.
The issue was not a lack of tooling, but a lack of clarity at the point where requests entered the system.
Constraints
- Fixed two-week delivery window
- Internal users only
- No dedicated design resources
- Required integration with existing tools and workflows
- Focus on function and clarity over visual polish
These constraints made it clear the solution needed to be lightweight, pragmatic, and immediately usable.
Key Decisions
- Use Jira as the final destination to avoid fragmenting existing workflows
- Define mandatory versus optional fields to reduce ambiguity without over-constraining users
- Guide input through structured forms instead of free-text requests
- Prioritize clarity and consistency over feature breadth
- Keep the solution simple enough to support immediate adoption
Each decision was made to minimize friction and improve downstream efficiency.
Early Technical Validation
Before defining any interface or workflow, the first step was validating technical feasibility. The solution needed to integrate with existing infrastructure rather than introduce a parallel system.
I evaluated whether Jira exposed the necessary APIs to programmatically create tickets with a consistent structure and metadata. This constraint shaped the entire approach: the internal application would act as a guided input layer, while Jira remained the single source of truth.
The goal was not only ticket creation, but ensuring that requests entering Jira met a consistent standard of quality across the organization.
Solution Overview
The resulting MVP was a lightweight internal tool that guided sales teams through a structured request flow. Instead of submitting unstructured information, users were prompted for the specific details required to create high-quality Jira tickets.
Behind the scenes, inputs were validated and used to create Jira tickets programmatically, ensuring consistent formatting and metadata across teams while fitting seamlessly into existing processes.
Outcome
- Clearer and more consistent incoming requests
- Reduced back-and-forth between sales and delivery teams
- Faster handoff from request to execution
- Lightweight solution adopted without disrupting established workflows
The MVP demonstrated that targeted process improvements can have meaningful impact even within tight time constraints.
Reflection & Future Considerations
This project reinforced how much leverage exists in improving internal workflows when constraints are embraced rather than avoided. Validating technical feasibility early and respecting existing systems made it possible to deliver value quickly without unnecessary complexity.
One potential extension discussed during the project was expanding the workflow beyond request creation into team composition. With structured project requirements already captured upfront, the same data could have supported assigning appropriate delivery teams based on skills, availability, and budget constraints. While this was outside the scope of the two-week MVP and did not progress further after my involvement, it highlighted how early process improvements can form a foundation for more strategic tooling over time.