Jash Shah Case study · Synthetic demo
Selected work / 01MGMTIO · Internal operations

Giving marketing work
a clear next step.

A command center for release and campaign coordination. One shared model, views shaped around the work, and a deliberate distinction between unknown and urgent.

Inspect the walkthrough
Contribution
Creator & builder · workflow systems
Intended users
Marketing & release operators
Evidence shown
Real components · synthetic data
Inside the execution viewLocal source render / c3e8af6
Actual MGMTIO component rendered with sample records. The Needs you queue offers Move campaign forward, Add promo outlets, and Post promo pages.
01 / A queue that turns campaign facts into explicit actions.Screenshot crop · Sample values are not results
01 / The problem

The work was connected.
The information wasn’t.

Campaigns, releases, pitches and imported records need to support a shared operating picture. An execution operator needs a next action; an operations lead needs ownership and timing; a decision-maker needs an overview.

Contribution

Jash Shah solely created and built MGMTIO, including its workflow design, data models, integrations, release validation and operating documentation.

He held the title Growth Marketing Analyst. Stakeholders supplied operating requirements, decisions and feedback; Jash also created the TasteLoop review process. [C01–C03]

The constraints

Imported records are not always active work. Manual checklists can be incomplete or stale. An internal product also needs a public explanation that keeps team and customer information private.

This demonstration uses a frozen source revision. No production system was connected for the demonstration.

02 / Decisions & tradeoffs

Make the next action
earn its place.

Three choices visible in the implementation. The tradeoffs below are a synthesis of that evidence.

01

Share the model.
Shape the view.

Execution, operations and executive views draw on one command-center model. Each foregrounds a different decision instead of giving every user the same dashboard.

The tradeoffMore view logic to maintain, with shared definitions that can be tested in one place.
Source note C04
02

Unknown does
not mean late.

An absent checklist remains “not tracked yet.” Dates, owners, statuses and placements can create work; blank tracking alone cannot manufacture an alert.

The tradeoffA calmer queue still needs people to keep the underlying tracking current.
Source notes C05–C06
03

Review imports
before they become work.

Notion intake stages records for review and target mapping before production creation. Import actions check existing mappings and use transactional writes.

The tradeoffManual review adds a step while keeping source ambiguity and duplicate creation visible.
Source note C07
03 / Inspect the result

Real components.
A safe walkthrough.

These are browser captures of committed React components, rendered locally with invented records. They are not mockups or a connected product demo.

Execution view with synthetic records: three explicit next actions and no invented cost-per-thousand result.
01 / Campaign facts become concrete actions.The sample queue distinguishes a campaign still in planning, missing promo outlets, and pages still to post. Unmeasured views leave cost per thousand as n/a.

Capture boundary

Source c3e8af6. Synthetic records replace private data before rendering. The capture wrapper, offline font fallbacks and disabled app links are disclosed adaptations. Authentication, data writes and integrations are outside this demonstration. View provenance

04 / Outcomes & limits

Working behavior.
Bounded claims.

Verified locally

Two actual component renders; eight rule assertions passed. Checks include no alert from blank tracking, excluding promo shells, and keeping fully posted work out of the posting queue. Inspect checks

Documented in source

Role-based views and a human-reviewed import path. A deployed environment is described in dated project notes. Current deployment was not checked, and the import path was not executed here.

Not measured here

Time saved, adoption, revenue and campaign lift. No quantified business outcome is claimed. Passing local checks does not establish production reliability or operational impact.

The recruiter version

From workflow requirements
to an inspectable system.

Jash Shah created MGMTIO for internal marketing and operations work. This case study shows shared data definitions, role-specific views and careful treatment of missing information, supported by source and a safe local demonstration.

Requirements · Data modeling · Workflow design · Validation
Evidence notes & AI assistance

12 claims and their evidence limits · Source boundary & capture adaptations · Page verification

The ledger separates creation, stakeholder input, implementation, deployment and measured outcomes. Original internal documents are not included.

How this case study was prepared

The case-study draft, synthetic fixture and capture harness were prepared with AI assistance. That assistance applies to this public presentation; Jash created MGMTIO and TasteLoop. Stakeholders contributed requirements and feedback.

Only invented demo records are shown. Original internal documents, application data and production screenshots are not included.

Read the evidence and disclosure boundary