MemoryMD · 2016 — 2020
Build with rigor.
Built the quality system and led regulatory work behind two FDA 510(k) clearances.
Quality systems · Regulatory executionHealthcare & AIFounder. AI engineer. Product & commercial leader.
AbdusMuwwakkil
I build AI products around how people think, decide, and work.
I’m a founder and hands-on engineer connecting interface design, commercial strategy, and research commercialization. I turn complex workflows into products people can understand, adopt, and use.30,023GitHub contributionsOct 2025 – Oct 2026
$3.1MARR generated & retainedAcross enterprise sales roles
$5M+Raised & helped raiseAcross founder and operating roles
2FDA 510(k) clearancesQuality & regulatory leadership
The throughline · 2016–present
Experience compounds.
Each role shapes how I build today. Select a chapter.
Skills & capabilities
Build. Commercialize. Lead.
Select a skill to see the tools, judgment, and work behind it.
AI engineering & design
Frontend & UX
- Interaction design
- React
- TypeScript
Design for divided attention, meaningful choices, and continuity between steps.
Applied in OrbVoice · Chef Mise · Lux Story
Applied AI
- Python
- FastAPI
- Deepgram
- Whisper
Speech, document extraction, and clinical drafts with review built into the workflow.
Applied in OrbVoice · Bill Analyzer · OrbBridge
Data systems
- SQL
- PostgreSQL
- Supabase
- Data analysis
Structure public datasets, compare benchmarks, and make findings traceable.
Applied in OrbDoc / NBC analysis · NCCI Check
Delivery
- Cloudflare
- Docker
- Playwright
- Vitest
Repeatable releases and checks across the mobile app, web platform, and backend.
Applied in OrbDoc · Klock
Commercial strategy
Human behavior
- Human factors
- Behavioral economics
- Customer research
Study recent behavior, current workarounds, and the decisions behind switching.
Applied in OrbDoc · Research ventures
Enterprise sales
- Salesforce
- HubSpot
- RFP strategy
Navigate complex buying groups, shape proposals, and develop long-term accounts.
Applied in Healthcare · Enterprise SaaS
Growth
- Media relations
- Content strategy
- Product-led growth
- GA4
Turn technical work into original analysis, earned media, and routes to a useful product.
Applied in OrbDoc / NBC reporting · Public tools
Partnerships
- Channel strategy
- Market entry
- Pricing & packaging
Build routes to market with clinical, technology, and distribution partners.
Applied in Medical devices · Healthcare software
Operating leadership
Teams
- Hiring
- Sales coaching
- Onboarding
Build teams and playbooks that make execution repeatable beyond one person.
Applied in Sales organizations · Venture teams
Regulatory
- FDA 510(k)
- ISO 13485
- Quality systems
Build the quality processes and regulatory foundations for medical-device market entry.
Applied in Medical devices · Clinical programs
Programs
- Workshop design
- Venture readiness
- Research commercialization
Teach founders to test assumptions, listen for evidence, and choose the next experiment.
Applied in NSF I-Corps · Morehouse / CBE
Operations
- Airtable
- Pipeline management
- Workflow automation
Connect people, records, and responsibilities in systems teams can run every day.
Applied in Program infrastructure · Commercial operations
Areas of focus
Complex industries.
Practical outcomes.
Four domains. Explore the systems I build and the decisions I help teams make.
01
Healthcare & applied AI
Technology that fitsclinical work
Clinical software, billing workflows, and medical devices.
Product & systems
Start with the clinical reality.
I used clinician and buyer interviews to redirect OrbDoc from hardware to software, focusing the product on documentation and billing workflows.
Discovery changed the productDocumentation · Billing · Patient engagement
Open OrbDoc Connect the entire experience.
I built OrbVoice so recording and note review work independently, then launched the clinical documentation app on the App Store.
App Store launchMobile · Web · APIs
Open OrbDoc Rules decide. AI explains.
I separated NCCI Check’s date-of-service billing rules from its explanation layer, so generated language cannot determine the result.
Deterministic billing checksNCCI Check · Date-of-service rules
Open OrbDoc Market & teams
Validate the problem early.
I analyzed inbound demand by specialty, buyer, and EHR, then created separate self-serve, enterprise, and partner sales paths.
Three buying pathsOrbDoc · Self-serve · Enterprise · Partners
Open OrbDoc Make readiness part of the plan.
I built the medical-device quality system at MemoryMD and led the work behind two FDA 510(k) clearances.
Quality & regulatory leadershipMemoryMD · Medical devices
Open OrbDoc Connect the product to adoption.
I launched clinical software with paying subscribers and early annual renewals, supported by free healthcare tools that brought prospective buyers to OrbDoc.
Paying subscribers & renewalsSelf-serve · Enterprise · Partnerships
Open OrbDoc Clinical product decisions
01Understand the workflowFind the need02Build the productBuild trust03Set the AI boundaryBring it to market
OrbVoiceOpen OrbDoc ↗
02
Enterprise & operations
Clarity forcomplex operations
From scattered information to decisions teams can act on.
Product & systems
Work with real operating data.
I built Klock to reconcile demand, supply, and inventory, then surface a recommended move with its rationale and missing inputs.
A recommended weekly decisionKlock · Planning spreadsheets
Explore Klock Make the next action clear.
I built Continuity to preserve who reviewed a decision and what supported it, connecting evidence ownership to the compliance lifecycle.
A connected compliance workflowContinuity · Readiness to reassessment
Explore Klock Put the workflow into use.
Klock reached pilot testing. Its interface centers the recommended decision so planners can move from inputs to a specific next action.
Built & pilot-testedKlock planning workflow
Explore Klock Market & teams
Start with the buying decision.
I interviewed users to identify enrollment drop-off, then used those findings to improve the experience and increase conversion.
Research improved enrollmentPropel · Customer interviews
Explore Klock Make growth repeatable.
I secured three national payer partners for a healthcare enrollment product and redesigned the sales process to shorten the sales cycle.
National payer partnershipsPropel · Medicaid enrollment
Explore Klock Connect the commercial team.
I hired and coached the sales development team, wrote its outbound playbook, and translated complex data into stories buyers could understand.
A playbook for the teamThinknum · Sales development
Explore Klock 03
Research & learning
Research witha route to market
Turn technical capability into customer evidence.
Product & systems
Ask about real behavior.
I teach teams to reconstruct a recent example: what happened, what workaround they used, what it cost, and who made the decision.
Customer-discovery curriculumInterview design · Workshops · Facilitation
Discuss commercialization Give the program a working system.
I built a linked program system covering people, teams, interviews, and opportunities, with reporting that separates attendance from completion.
Program infrastructureLinked records · Reporting · Workflow automation
Discuss commercialization Make learning something you do.
I designed Lux Story so choices change trust and the next scene, then become contextual observations a learner can discuss with an advisor.
Interactive EdTechLux Story · Independent EdTech project
Explore Lux Story Market & teams
Make technical potential useful.
Through NSF I-Corps, I coached eight Summer teams on customer discovery across materials, industrial technology, care, education, and consumer products.
8 Summer teams coachedDelivered coaching · Summer 2026
Discuss commercialization Find who can approve adoption.
I help founders distinguish users, buyers, and blockers, then test what would make adoption possible—or rule it out.
Customer and adoption decisionsCustomer interviews · Segmentation · Buying incentives
Discuss commercialization Choose the next useful step.
I connect customer evidence to product requirements and the next test. Teams decide whether to narrow the market, run a pilot, keep learning, or pause.
Product definition and commercializationWorkflow mapping · Interface requirements · Market discovery
Discuss commercialization 04
Everyday experiences
Useful ineveryday life
Cooking, exploration, and the details that make an interface useful.
Product & systems
Design around real attention.
In Chef Mise, I put scaled ingredients, timers, and sensory cues beside the current step, designing for a cook whose attention is divided.
Experience designMobile use · Clear navigation · Task focus
Open Chef Mise Keep the next step within reach.
I built persistent shopping state in Chef Mise, keeping lists and checked items available across sessions in guest and signed-in modes.
Shopping state that persistsGuided workflows · Responsive design
Open Chef Mise Make the idea tangible.
I built UForage’s local scouting notebook with observations, photos, and portable exports, so captured records can leave the app.
Portable field recordsUForage · Local scouting notebook
Open Chef Mise Market & teams
Choose a specific use.
I start with the activity: preparing dinner, exploring a place, or considering a career. That context shapes what the product asks people to notice and do.
Product strategyAudience · Use case · Scope
Open Chef Mise Give each audience a clear route.
I gave UForage two distinct entry points: an event experience and a Long Beach scouting notebook, each organized around its own use case.
Product positioningConsumer needs · Clear entry points
Open Chef Mise Carry the idea through execution.
I carry these products from concept through interface design and implementation. The project gallery shows the resulting experiences and technical choices.
End-to-end ownershipConcept · Design · Development
Open Chef Mise How I build
Hands-on.
End to end.
I turn domain knowledge into working software: interfaces people can navigate, data they can trace, and decisions they can review. I build across mobile, web, and backend.
Design for attention
Chef Mise keeps quantities and cooking cues beside the current step. Lux Story connects choices to consequences. Human factors shape the interaction, not just the appearance.
Own what ships
I use AI to build across the stack. I define the outcome, inspect the changes, test the workflow, and take responsibility for the release.
Rules decide. AI explains.
NCCI Check evaluates billing rules for the date of service, with a separate explanation layer. Klock separates planning calculations from optional AI review. Clinical drafts remain subject to clinician review.
30,023
GitHub contributions
Oct 12, 2025 – Oct 12, 2026
Hands-on work across products, prototypes, infrastructure, tests, and releases.
Explore my GitHub ↗Selected projects
Built around
real work.
Products for clinicians, operators, learners, and people trying to get something done.
For clinicians
OrbVoice
Keep the conversation connected to the clinical note.
I built the mobile, web, and backend workflow from recorded encounter to reviewable draft, keeping audio capture separate from note generation.
What it enables
Recover from processing failures while keeping clinicians in control of the final note.
- Clinical UX
- Recovery workflows
- Mobile architecture
- React Native
- Expo
- Python
- FastAPI
Inside OrbVoice
Separate the recording from the note.
Each recording has an identity, local file, and upload state. A separate processing queue checks ownership, reuses completed uploads, and keeps retry context. Capture and document generation have distinct lifecycles, so a failed processing step can be retried without starting a new encounter.
For supply-chain planners
Klock
Turn scattered spreadsheets into a weekly decision.
I translated supply-chain planning into a decision workflow: reconcile spreadsheet inputs, identify shortages or excess, and propose an action with its constraints.
What it enables
See what to act on, what information is missing, and what needs approval.
- Decision systems
- Data normalization
- Operations modeling
- Next.js
- TypeScript
- React
- Zod
Inside Klock
Calculate the move. Preserve the decision.
Workbook normalization feeds deterministic planning rules. Missing inputs surface as repair tasks; recommendations retain source references and rationale. Approval and export eligibility remain explicit states. Estimates are planning aids, not realized savings; optional AI review is separate from the calculations.
For defense contractors
Continuity
Keep decisions defensible as requirements change.
I modeled compliance as an ongoing operating cycle, connecting scope, evidence owners, contract readiness, annual decisions, and reassessment.
What it enables
Reconstruct what was reviewed, who decided, and which evidence supported the decision.
- Domain modeling
- Authorization
- Auditability
- Next.js
- PostgreSQL
- Drizzle
- Zod
Inside Continuity
Preserve what a decision was based on.
Permission and version checks precede annual decisions. A hashed snapshot preserves declarations and review state; exports carry checksums, and official submissions are recorded separately. Evidence references stay distinct from raw controlled information. This supports compliance operations; it does not grant certification.
For learners and career advisors
Lux Story
Give career conversations something concrete to build on.
I designed a narrative system where choices change character trust and the next scene, creating contextual observations for reflection with an advisor.
What it enables
Discuss what a learner chose, in context, and what they might explore next.
- Experience design
- Narrative systems
- Evidence-grounded AI
- Next.js
- TypeScript
- React
- Supabase
Inside Lux Story
Keep the context behind each choice.
A choice transition coordinates story state, trust, and scene-specific observations. Advisor briefings draw from canonical server records rather than client-supplied profiles, preserving uncertainty when evidence is sparse. Authored skill tags support reflection, not validated proficiency or personality scores.
For home cooks
Chef Mise
Design for the cook with their hands full.
I connected pantry choices, shopping, and guided cooking around divided attention: the right quantities, the current step, and cues for what to notice.
What it enables
Turn a meal idea into a shopping list and a sequence you can pause and resume.
- Human factors
- Ingredient modeling
- State continuity
- Next.js
- Supabase
- Zustand
Inside Chef Mise
Carry context from the pantry to the pan.
Pantry matching distinguishes required ingredients from optional items. Shopping lists merge compatible quantities while retaining recipe sources. Cook mode carries scaled ingredients into steps, timers, sensory cues, and saved progress—connecting data modeling to the demands of a busy kitchen.
For event operators and local explorers
UForage
Connect discovery to a useful next step.
I built two spatial workflows: an event guide connecting visitors with vendors and sponsors, and a Long Beach notebook for field observations and follow-up.
What it enables
Help operators understand guide engagement and explorers keep portable records.
- Spatial UX
- Engagement analytics
- Local data integrity
- Next.js
- MapLibre
- IndexedDB
Inside UForage
Match the record to the real-world task.
The event demo validates interactions against its published guide before reporting engagement, not attendance or purchases. The separate notebook uses version-checked IndexedDB transactions to reject conflicting writes and confirms saves after commit. JSON/CSV exports make browser-local records portable.
Growth, PR & distribution
Build the product.
Reach its audience.
I connect engineering, original analysis, media relations, and community to give useful products a route to market.
OrbDoc · Data engineering, PR & growth
Turn the analysis
into a national story.
At OrbDoc, I led hospital-pricing analysis for Pulitzer Prize-winning journalist Gretchen Morgenson’s NBC News investigation.
The report credited our analysis, quoted me, and linked our free Bill Analyzer—connecting technical work to public visibility and a useful product.
Featured in NBC News’ homepage Editors’ picks.
Inside Bill Analyzer
I built a medical-bill OCR pipeline on open-source components, with custom logic for interpreting charges and checking them against CMS references.
- Read the document. Browser OCR and bill-specific extraction turn images into editable lines.
- Establish the context. Coding checks and qualified Medicare references help identify questions to review.
- Support the next conversation. People verify the extracted details and take focused questions to their billing office.
TypeScript · React · Tesseract.js · PDF.js · CMS data
02 / Reach
Millions of readers
Report readership, per Gretchen Morgenson.
03 / Put it to use
Bill Analyzer
Custom document extraction, billing-rule checks, and CMS references help people make sense of a medical bill.
Content that gets a response.
Useful tools. Timely questions. Stories worth sharing. I work across formats to give people a reason to engage.
Across 11 selected posts
- Displayed views
- ≈407.7K
- Net upvotes
- 1,306
- Comments
- 392
- Shares
- 297
Rounded views may include repeat viewers. Upvotes shown as Reddit net scores. Captured .
D.R.E.A.M.
Data, in another register.
I wrote and performed a data rap with the Business of Business, using music and satire to bring a technical subject to another audience.
Read the making-ofBuilding Through the AI J-Curve
Why adopting AI means redesigning the work around it: processes, ownership, and how results are judged.
Read the essayPresent to Persuade
I moderated a conversation with Jason Forrest and Jarrett Hurms on W.E.B. Du Bois’ visualizations, then wrote about evidence, audience, and representation.
Read the discussion recap