Who I am
I'm Mehdi — [CREDENTIALS], and I've been building products on the web for [YEARS BUILDING]. [CURRENT ROLE].
I'm not a developer by trade. I'm a founder who builds with visual tools because they let me move fast and ship real products without a full engineering team. That perspective shapes every word on this site: I'm not evaluating tools in theory, I'm building with them.
I run two editorial projects: this one — shipwithout — focused on visual builders for non-dev founders, and stackrev.net, which covers the developer stack (APIs, databases, hosting, automation tools). Same editorial independence, different audiences.
Why shipwithout exists
The no-code review space has a problem. Most sites fall into one of three traps:
Vendor capture. The "best tools" list is written by whoever pays the highest affiliate rate. The top result isn't the best tool — it's the most profitable referral.
AI-generated noise. The review was scraped from marketing copy and published the week the tool launched. No one tested anything. It reads like a press release because it basically is one.
Wrong lens. The reviewer is a developer who thinks "easy" means "I didn't need a framework." That doesn't help a founder who wants to build a client portal without hiring a dev.
I built shipwithout because I couldn't find a site that reviewed visual builders from the perspective of someone actually using them to build things. Not someone evaluating them for sport — someone who needs to choose a tool and then live with that choice in production.
The commitment I make to you: every tool I review, I've used to build something. Pricing is verified at publish and stamped with a date. Affiliate links are disclosed at the top of the page, before you read a word. No tool pays for placement. My income comes from reader trust, not vendor fees.
What I cover — and what I don't
Shipwithout covers visual builders that produce end-user-facing products: site builders, app builders, e-commerce platforms — tools that let you create something another person will pay to use.
Three content formats, each with a specific job:
- Compare — Head-to-head between two tools for a specific use case. Who wins, for whom, and why the other option still has a place.
- Decide — Strategic playbooks for tool selection. "I want to build X without code — what do I use?" answered with concrete recommendations, not hedge-everything framework thinking.
- Learn by example — Real founder case studies: what was built, with which tool, what the tradeoffs looked like after six months in production.
What I don't cover: automation tools, databases, APIs, backend infrastructure, or hosting platforms. That territory belongs on stackrev.net. I cross-link when it's relevant, but the two sites have separate editorial scopes — no blurring.
All visual-builder content lives in the site-builders section — coming soon.
How I review
Every review follows the same four steps:
1. Hands-on build. I build a reference project on the tool before writing a word. Not a toy. A real use case — the kind a founder might actually ship. If I can't get it working, I say so.
2. Pricing verification with a timestamp. Pricing in this space changes constantly. Every review stamps the date I checked. If you're reading this six months after publish, check current pricing before you buy.
3. Affiliate disclosure up front. If I earn a commission when you click a link, it's disclosed at the top of the page — not buried in a footer. You know before you read, not after.
4. No pay-for-placement. I don't take sponsored content. Tools don't pay to appear in my comparisons. Ranking is editorial, not commercial.
The full methodology — including how I structure hands-on tests and what I look for in a tool — is on the How I test page.
Get in touch
I'm easy to reach.
- Email: coming soon
- LinkedIn: coming soon
- X / Twitter: coming soon
If you've shipped something with a visual builder and want to share what worked (and what didn't) for a case study, I'm especially interested in hearing from you.