Built by one person, close to the actual work

Software with a point of view.

Morgan Labs builds focused tools for merchants, operators, and small teams who need software that solves the real bottleneck instead of performing startup theater around it.

Shipping, preview, and lab work labeled clearly Small surfaces, fast feedback Useful tools over generic software theater

Project status

One map of what is live, submitted, previewing, or still in the lab.

The maturity labels matter. Shipping products get the most weight, submitted apps are clearly marked, previews are honest previews, and lab utilities stay compact until they have a stable public home.

This status table is intentionally boring: one row per public surface, one maturity label, one useful next link. No invented traction, no fuzzy “live” status doing five different jobs.

1 Shopify App Store live product 3 Shopify review surfaces 3 non-Shopify public surfaces
01 / studio
MorganLabs Site morganlabs-site
Studio home

The public web surface for Morgan Labs, including project framing and legal pages.

View public repo
02 / live
ReturnSense returnsense-validation-starter
Shopify live

Return-reason analytics, reviewed product-page fixes, and before-and-after monitoring for Shopify merchants.

Open live site
03 / review
PackBridge packbridge
Submitted

Submitted Shopify app for post-order B2B pack-unit translation, workflow normalization, and signed outbound payloads.

Open live site
04 / review
Script Sentinel script-sentinel
Submitted

Submitted Shopify Plus app for read-only Scripts-to-Functions parity evidence, fixture coverage, and drift review.

Open live site
05 / review
StockLock stocklock
Submitted

Submitted Shopify app for paired-store inventory sync, SKU mapping review, sync logs, and discrepancy handling.

Open live app surface
06 / preview
HubSpot Platform Sentinel hubspot-platform-sentinel
Preview

Read-only HubSpot platform migration scanner for deadline-ranked evidence packs.

Open live preview
07 / live
Equipoise equipoise
Non-Shopify

EU Pay Transparency Directive readiness workflow for reviewable evidence, job-posting checks, and report preparation.

Open live site
08 / lab
CriticalPatcher critical-patcher
Lab URL

Temporary live Salesforce critical-update patcher surface hosted on the production droplet while its branded domain is pending.

Open temporary site

Method

Small studio rules, on purpose.

The studio stays lean so product decisions can stay close to the problem. Fewer layers means faster truth: what helps, what confuses, and what needs to be removed.

Start with the bottleneck.

Every build begins where real work gets stuck, not where a pitch deck wants a feature to exist.

Keep the surface area tight.

If a tool needs a tour before it can help, it is probably carrying too much weight already.

Ship early enough to learn.

Useful v1s beat polished abstractions. Feedback is better when the thing can actually be used.

Studio notes

Independent, but not vague.

Morgan Labs is intentionally independent, but the site still has to do grown-up work: explain what is shipping, what is early, what data each product touches, and how to reach a human when something matters.

That means practical support pages, truthful copy, release notes that match reality, and products that stay readable even when the problem underneath them is messy.

What matters here Updated April 2026
Support
Direct contact beats support theater.

Questions, reviews, and merchant issues route straight to a real builder, not a fake enterprise shell.

Privacy
Policy pages should match the actual apps.

The privacy policy stays close to the actual apps and support surfaces instead of pretending every lab build collects the same data.

Build
The product is the portfolio.

No generic agency case studies here. The best proof is the software itself, the constraints it respects, and the workflows it improves.

If you have a sharp problem, that is the right way to start.

Morgan Labs works best on workflows that matter and still feel underserved: merchant ops, catalog control, review-heavy tooling, and weird edge cases that larger software keeps flattening into generic templates.