Omar Farouk.
Scopes and leads selected client builds, and helps startups and agencies decide what to build first.
Engagement Lead, Services
At the studio since 2022
What Omar does at the studio.
Omar leads the studio's selected engagements: the product builds, integrations, and technical partnerships taken on for a small number of teams each year. Their focus is scope, the written problem, the named operator, and a handover that leaves a system the client can run alone.
With a background in agency delivery and startup product engineering, Omar has seen both sides of the buying conversation, and writes guides intended to help buyers ask better questions of any studio, including this one.
Omar writes about scoping, build-versus-buy decisions, and how agencies can add capabilities like payments to client projects without taking on the wrong kind of responsibility.
Posts by Omar.
What agencies should know before adding payments to a client project
Clients ask for 'a payments option' as if it were a plugin. It is a long-lived responsibility. Here is how to scope it without becoming a payments company.
By Omar Farouk
Paying contractors in stablecoin: an operational playbook
Faster settlement is easy to promise. The hard part is approvals, records, and an ERP that still has to balance. Here is how a field-services company did it.
By Omar Farouk, Layla Haddad
Is this internal tool worth building? A worksheet for operations leaders
Before you commission software, put a number on the workaround. A five-step way to decide whether to build, buy, or leave the spreadsheet alone.
By Emily Sinclair, Omar Farouk
How to choose a software studio: twelve questions to ask before you sign
Portfolios look the same. These questions do not — they surface how a studio scopes, communicates, and hands over.
By Omar Farouk
How to scope an MVP that actually ships in six weeks
A practical method for cutting a product down to the smallest complete system — and writing down what you are not building.
By Omar Farouk
A buyer's checklist for evaluating a self-hosted payment gateway
Thirty questions to ask before you deploy anything that can move money — sorted by what they reveal.
By Omar Farouk, Daniel Whitfield
Build, buy, or rent: a decision framework for payment infrastructure
Three options, six criteria, and a scoring sheet you can fill in before the next vendor call.
By Omar Farouk, Layla Haddad
More authors.
Layla Haddad
Principal Engineer, Payments Infrastructure
Designs the gateway architecture behind StablePay: state machines, indexing, and signing boundaries.
Daniel Whitfield
Staff Engineer, Platform & Reliability
Owns webhooks, PostgreSQL, deployment, and the operational habits that keep self-hosted software boring.
Emily Sinclair
Head of Product
Leads Northframe and Meridian, and the discovery work that turns shadow spreadsheets into products.
Mohamed Hasan
Design & Frontend Lead
Leads interface design and frontend engineering across the catalog, with a focus on dense, calm operator UIs.
Mohamed Saad
Smart Contract Developer
Works on the on-chain side of payments: token transfers, event interfaces, and contract review for products that touch a chain.
El Sayed Abd Almohaymen
Mobile Developer
Builds mobile experiences that put approvals, queues, and payment status in the hands of people who are not at a desk.
Have a system like this to run?
Explore the catalog, or write down the problem and the constraints. We respond when the fit is real.