Operator accountability, program leadership, cross-functional delivery, and systems-building across technology, operations, launches, and founder-led ventures.
This repository contains the source for Sama Mushtaq's public portfolio. The site is designed for Program Manager and Project Manager recruiting conversations and emphasizes business stakes, mandate, decisions, delivery systems, adoption, and evidence rather than a gallery of outputs.
- Deployment: live public static site on GitHub Pages
- Audience: Program Manager, Project Manager, and cross-functional operations hiring teams
- Content status: selected cases and resume are published
- Evidence discipline: claims are separated into dated snapshots, operating records, founder-reported aggregates, reconstructions, and illustrative prototypes
Sama's operating pattern is consistent across industries:
- Frame the business outcome and baseline.
- Translate ambiguity into workstreams, owners, dependencies, and acceptance criteria.
- Align stakeholders around tradeoffs and decision rights.
- Establish a governance cadence for risks, metrics, and escalation.
- Build training, documentation, and ownership into delivery.
- Measure the result and institutionalize what worked.
- Mandate: Co-Founder and Program Lead responsible for field workflow, product requirements, vendor delivery, acceptance, and reporting direction.
- Evidence: Vendor-built dashboard prototype, sanitized workflow reconstruction, and reconstructed delivery roadmap.
- Evidence boundary: Pilot and program facts are aggregate operating claims. Dashboard values are fictional sample data.
- Mandate: Operations Manager, promoted to Assistant General Manager and Acting General Manager. Led financial controls, workforce capability, adoption, and management cadence.
- Evidence: Original server-certification artifact plus sanitized operating-model reconstruction.
- Evidence boundary: Aggregate operating results are leadership-account claims. Confidential P&Ls and employee records are withheld.
- Mandate: Director of Operations and Launch Consultant, not owner or founder.
- Evidence: Sanitized launch roadmap, operating photo, pricing system, layouts, menu, and process evidence.
- Evidence boundary: Aggregate launch outcomes are operating-record and leadership-account claims.
- Mandate: Founder and Program Lead responsible for brand, acquisition, onboarding, curriculum, membership, retention, and platform migration.
- Evidence: Direct Stripe snapshots and sanitized platform reconstruction.
- Evidence boundary: Approximately 2,000 peak community members and more than 1,200 cumulative paid subscribers across the program lifetime are founder-reported aggregates. MRR and active-subscription figures are dated Stripe snapshots.
- Alcohol pricing decision system: invoice-to-pour-cost and POS pricing workbooks.
- Crew scheduling engine: sanitized representative reconstruction of operational tooling used to produce posted schedules.
- Restaurant Imaging program: standards corrective-action cadence, ownership, photo evidence, and re-walk governance.
- Casino steakhouse analytics: redacted beverage-profitability business case and capability programs.
- Restaurant buildout: operating workstreams and artifacts from the iTZCALi launch engagement.
The portfolio uses explicit provenance labels so visual polish is not mistaken for stronger proof than the source supports.
- Documented platform snapshot: Direct capture from a source platform at a specific point in time.
- Operating record: Aggregate result supported by historical operating materials that remain private.
- Leadership-account claim: Result reported from Sama's management records or direct operating knowledge. It is not independently audited in the public repository.
- Original artifact: Historical work product shown substantially as created, with publication review.
- Sanitized original: Historical artifact with identities, confidential values, or sensitive fields physically removed.
- Reconstruction: Retrospective recreation of the operating model after sensitive details were removed.
- Representative sample: Fresh output created from anonymized or substitute data while preserving system behavior.
- Illustrative prototype: Product or interface concept containing fictional or sample values. It is not evidence of business results.
index.html: Portfolio homestyle.css: Shared visual system and responsive layoutscript.js: Navigation, interaction, and print behaviorimages: Reviewed public evidence and site imagerywork/rygneco: Zero-to-one product program casework/hard-rock: Operational transformation casework/itzcali: Restaurant launch casework/mak-trading: Community and recurring-revenue caseresume/index.html: Web resumeresume/*.pdf: One-page formatted resumescripts: Build, validation, and resume-generation scriptspackage.json: Local validation and build commands
Requirements: Node.js for site validation and the documented Python/PDF dependencies only when rebuilding the resume PDF.
npm run check
npm run buildnpm run checkruns the repository's static checks.npm run buildproduces the validated static-site output.
Review the home page, every case page, the web resume, and the PDF at desktop and mobile widths before deployment. Evidence images require a separate visual privacy review because automated checks cannot determine whether an identity should be public, and CSS cropping is not treated as source-file redaction.
Sama Mushtaq supplied the source records, career context, operating decisions, claim approvals, and final acceptance for this portfolio. The underlying programs were delivered with employees, managers, co-founders, vendors, contractors, advisers, and system partners as identified in each case.
The portfolio distinguishes between:
- Work Sama personally authored or led
- Work implemented by vendors or collaborators under his program direction
- Reconstructed presentation artifacts
- Direct platform evidence
- Aggregate claims whose detailed records remain private
The portfolio does not claim that Sama personally wrote every line of vendor software, performed every frontline task, or created third-party platform interfaces.
AI tools assisted with portfolio research, information architecture, writing, coding, document generation, and testing. Sama provided the source material, corrected role and metric details, decided what could be published, and accepted the final result.
AI assistance in presenting the portfolio is not presented as authorship of the underlying historical operating work. Individual supporting repositories disclose AI involvement in the original work where the public record establishes it, including the crew scheduling and Restaurant Imaging programs.
- No employee roster, applicant record, payroll record, client inventory, device identifier, confidential P&L, or trading-performance record should be published.
- Prototype figures must remain labeled fictional or illustrative.
- Aggregate metrics must retain their evidence labels and time boundaries.
- Vendor-implemented interfaces must not be described as personally coded by Sama.
- Redaction must occur in the source artifact, not only through CSS or layout.
- Any new artifact requires both content review and visual privacy review before deployment.
- This is a self-authored professional portfolio, not an independent audit.
- Selected evidence is intentionally incomplete because detailed employer, employee, client, and member records remain private.
- Some outcomes are leadership-account claims rather than directly published source records.
- Reconstructed visuals explain operating systems but are not substitutes for original evidence.
- The site presents selected programs and does not represent every role or project.
No license is currently granted for personal photographs, resume content, case-study text, brand materials, or evidence images. If source code is intended for reuse, add an explicit code license and separately state that personal content and media remain excluded from that license.