Localized Creative Hiring MVP Built in Two Weeks

The challenge

A founder approached CVision with a clear market angle: make it easier for vendors in Pakistan to discover and hire creative talent through a structured product instead of scattered conversations across WhatsApp, Instagram, and informal networks.

The creative ecosystem has real depth—but discovery and trust break down when everything lives in DMs and one-off referrals. That produces predictable friction:

• Low trust without a shared, reviewable surface.
• Poor discovery when opportunities are invisible outside private threads.
• No structured matching—people repeat the same outreach work from scratch.
• No scalable hiring workflow vendors can rely on.

Without a working platform, the idea stays stuck in concept mode. The goal was not a bloated product—it was market validation with something deployable, fast.

What CVision identified

This was not a “add more features” problem. It was a structure problem.

Talent and demand were not missing—a native, repeatable workflow to connect both sides was. The product had to prioritize core marketplace logic first: identity, intent, discovery, and a path from interest to hiring—before secondary integrations.

The build thesis: ship the smallest credible system that makes hiring legible on both sides, then extend—rather than front-loading complexity that delays learning.

What we built: Sanjh

CVision delivered a full-stack marketplace MVP around two primary user groups, with shared platform services underneath.

Talent-side flow

• Sign up and build a profile with portfolio and identity details.
• Browse relevant jobs and apply—or be surfaced to vendors through discovery.

Vendor-side flow

• Sign up and express hiring intent.
• Post jobs, review proposals, and discover talent through platform matching.
• Move toward hiring through a structured workflow instead of ad hoc threads.

Platform capabilities (MVP)

• Authentication and account system.
• Profile creation and management; profile completeness logic.
• Search and discovery; structured category system.
• AI-assisted matching with filters and tagging.
• Messaging and booking-oriented workflows.
• Admin panel, onboarding flow, and moderation controls.

Product decisions that mattered

Delivery was scoped to roughly two weeks. That forced explicit tradeoffs—on purpose.

Prioritized:

• Core user journeys end-to-end.
• Structured discovery and usable profiles.
• Backend and data model readiness for deployment and iteration.

Deferred (v1):

• Unnecessary external integrations that do not unblock validation.
• Payment gateway complexity in the first version—keeping focus on workflow and liquidity mechanics first.

Why this was more than a demo

This was not a mockup or a marketing landing page dressed as a product.

• Hosting readiness and a structured database design.
• Completed authentication and role-appropriate access patterns.
• Admin controls and operational hooks (moderation, categories).
• Documented handoff and maintainable architecture for the next phase.

In practical terms, the client received a deployable product foundation that could be launched and extended—not a slide deck with screenshots.