SaaS & web platforms
Multi-tenant products with roles, permissions, billing, and audit trails designed in from the first migration — not patched on after the first customer asks.
Software · Marketing
We build the product. Then we build the demand.
Midadd is a product engineering studio with a growth team inside. We design, build, and run web platforms, SaaS products, and internal tools — then put them in front of the people who need them. One team, one backlog, no hand-off.
- TypeScript, React & Node.js
- Staging-first releases
- You own the code from day one
01 — The gap
Most products die between “it works” and “people use it.”
Dev shops hand you a repository and an invoice. Agencies sell you traffic for a product that can’t convert it. Somewhere in between, launches stall, tracking breaks, and nobody owns the outcome.
Midadd closes that gap. The engineers who build your product also wire its analytics, ship its landing pages, and sit in the growth reviews. When a campaign underperforms, we fix the funnel in code the same week — instead of opening a ticket with another vendor.
02 — What we build
Engineering is the core. Marketing is the multiplier.
Most of our work is software. All of it is built to be found, used, and measured.
Software engineering
Internal tools & operations systems
Replace the spreadsheets running your business with software that matches how your team actually works: approvals, finance, HR, inventory, and reporting.
Integrations & automation
Payments, messaging, CRMs, and webhooks connected into workflows that run on their own — so nobody copies data between tabs at 6 p.m. again.
AI features inside your product
Assistants, document processing, and search built on your own data, with permissions and guardrails — not a chatbot bolted onto your homepage.
Cloud, DevOps & hardening
Linux servers, Nginx, CI, backups, monitoring, and security reviews. We take over fragile deployments and make them boring — in the best way.
Codebase rescue
Inherited code nobody wants to touch? We audit it, stabilize it, and keep shipping features while we pay down the debt that slows you down.
Growth marketing
Launch & go-to-market
Positioning, messaging, and a launch plan grounded in what the product actually does well.
Conversion landing pages
Fast pages built by engineers, instrumented from day one, and tested against real traffic.
Performance campaigns
Google and Meta campaigns managed against conversions in your database — not impressions.
Analytics & attribution
Event tracking, server-side signals, and dashboards that finally agree with your numbers.
03 — Engineering standards
Rules we don’t break — even when the deadline is tomorrow.
Process is easy to promise. These are the specific habits that keep your product stable after launch day.
done === proven
Nothing is marked done without live evidence: an API response, a database query, or a real session in the browser. A status update is not proof.
review(diff)
Every change is read line by line before it reaches production. We review the actual diff — never just the summary of what changed.
authorize(onServer)
Permissions are enforced on the server for every request. Hiding a button in the interface is not access control.
staging → production
Every release lands on staging first, where you click through it before your customers ever see it.
fix(pattern)
When we find a bug, we search for the same pattern across the codebase before we close it. One fix, every occurrence.
owner: you
Your repository, your servers, your cloud accounts — from the first commit. No lock-in, no hostage code, no surprise hand-over fees.
04 — Then we grow it
Marketing with access to the source code.
Because we built the product, we don’t guess what happens after the click. We instrument every key event, ship landing-page experiments in days, and judge campaigns by revenue in your database — not by impressions in an ad dashboard.
- Tracking lives in the codebase. Version-controlled, reviewed, and tested like any other feature.
- Funnels change in the same sprint. Landing pages and onboarding move as fast as the campaign that drives them.
- Engineers sit in the growth review. Every week, the people who can fix the product hear what the data says.
05 — How a project runs
From first call to first customer.
-
01
Scope
A working session to map users, risks, and the smallest version worth shipping. You get a written scope: what’s in, what’s out, and why.
-
02
Build
Short cycles with a live staging link. You see working software every week — not slide decks or progress percentages.
-
03
Ship
Security checks, verified backups, and a release you’ve already tested. We go live together and watch the first hours closely.
-
04
Grow
Analytics, launch campaigns, and iteration on what real users do. Same team, same backlog, no hand-off.
06 — Ways to work with us
Pick the shape that fits your stage.
Every engagement starts with a scoping call. You get a fixed quote before any work begins.
For a new product
Product Build
Fixed scope and timeline. Best for an MVP, a new platform, or a well-defined internal system.
- Discovery & written scope
- Design, build & staging
- Launch with monitoring
- Post-launch support window
For an evolving roadmap
Product Team
A dedicated monthly team that ships features, maintains infrastructure, and owns quality.
- Reserved engineering capacity
- Weekly demos & planning
- DevOps & maintenance included
- Growth support when you need it
For a product that should sell more
Launch & Growth
For products that work but don’t grow yet. We fix the funnel first, then scale what converts.
- Funnel & tracking audit
- Landing pages & experiments
- Paid campaign management
- Monthly growth report
Tools we trust
Technology stack
- TypeScript
- React
- Node.js
- Express
- tRPC
- Drizzle ORM
- MySQL
- Tailwind CSS
- Vite
- Linux
- Nginx
- PM2
- Git
- n8n
- LLM APIs
- Google Ads
- Meta Ads
- GA4
- Tag Manager
07 — Why “Midadd”
Midad (مِداد) is Arabic for ink.
For centuries, ink was how ideas became real — contracts, ledgers, books, maps. Code is the ink of our time. We chose the name as a reminder of the job: take an idea that only exists in someone’s head, and write it into something people can use.
Do we own the code?
Yes. Everything lives in your repository and your accounts from the first commit. If we ever part ways, you keep working without asking us for anything.
Can you take over an existing codebase?
Often, yes. We start with a short paid audit covering architecture, security, deployment, and the riskiest areas. Then you decide — stabilize, refactor, or rebuild — with the trade-offs written down.
Do you only market products you built?
No. But we always review the product and its tracking first. Sending paid traffic to a funnel that leaks is the most expensive mistake in marketing.
How do you price projects?
Fixed-scope builds get a fixed quote after scoping. Product teams and growth work are billed monthly. No open-ended hourly surprises.
How do we communicate across time zones?
We work remotely and async-first: written updates, a live staging link you can check anytime, and scheduled calls inside your working hours.
What do you need from us to start?
A 30-minute call, any existing documents or designs, and one decision-maker who can answer questions within a day. That’s it.
Start a project
Have a product to build — or one that should be growing faster?
Tell us where you are. We’ll come back with honest next steps — even if that means we’re not the right fit.
Prefer email? hello@midadds.com