Work With Me
I build the product and get it traffic
Most teams hire a developer to build the thing, then hire someone else to make people find it. I do both.
I'm a full-stack developer who ships production software — payment systems, custom WordPress, React and Node applications — and then takes it from zero organic traffic to sustainable search demand. Not two vendors with a handoff between them. One person who owns the outcome.
Based in Tel Aviv · Working with clients globally · Native English
Services
What I do
Most projects touch more than one of these. That's the point — you don't have to coordinate between a dev shop, a WordPress contractor, an AI consultant, and an SEO agency.
Custom AI integration
LLM features that survive real traffic — support agents, grounded answers over your content, and cost-controlled model routing. Claude, OpenAI, or self-hosted. Running in production on my own SaaS today.
AI integration →Web applications
Frontend and backend by the same person. React, Next.js, Node, TypeScript, PHP. API integrations, database migrations, real-time features, Chrome extensions.
Application development →Custom WordPress
Gutenberg blocks, custom themes, and plugins built properly — not page-builder bloat. WooCommerce, payment gateways, WPML multilingual and RTL, headless setups.
WordPress development →Payment integrations
Stripe billing, Meshulam, custom WooCommerce gateways, and crypto. I built a payment system processing over $1M a year, and run Stripe billing on my own products.
Payment integrations →SEO & organic growth
Zero to one. Technical SEO, keyword architecture, content structure, internal linking, and authority building — measured in real rankings, not vanity reports.
SEO & growth →Idea to first payment
The whole arc for founders: scope, build, landing pages, Stripe billing, launch, then iterate — new pages, new features, a brand that compounds over quarters.
Product launch →Why It Matters
Shipping and being found are the same project
The usual split causes real damage. The dev team builds a fast single-page app with one URL, and there's nothing for Google to index. The SEO agency asks for thirty landing pages, and the dev team quotes six weeks because the templating wasn't built for it. Both are right. Neither owns the outcome.
When one person does both, the architecture decisions get made with search in mind from day one — URL structure, rendering strategy, internal linking, page templates you can actually extend. And when a keyword opportunity shows up eight months later, shipping the page takes an afternoon instead of a sprint.
I've done this on my own products, which is the honest reason I can claim it. GhostChat, Gmailytics, and KaspaWoo were built, launched, and grown by one person — product and organic growth both.
How We Work Together
Engagement models
Pricing depends on scope, so I quote after a conversation rather than publishing a rate card that would be wrong for your project.
Project build
A defined thing, delivered. A plugin, an integration, a marketing site, an MVP. Fixed scope, milestone-based, with a written spec before anyone writes code.
Ongoing retainer
For products that need continuous work — shipping features, adding pages, watching Search Console, and iterating on what the data says. This is where compounding growth happens.
Audit & rescue
Something is broken, slow, or silently losing you traffic. I diagnose it, document what I find, and either hand you the fix list or implement it.
Process
What working with me looks like
- A real conversation first Thirty minutes on what you're actually trying to achieve. If I'm not the right person, I'll say so — I'd rather tell you in the first call than the third invoice.
- A written scope What gets built, what doesn't, what it costs, and when it lands. No code starts before we both agree on this document.
- Build in visible increments You get a working preview URL early and it updates continuously. No four-week silences ending in a surprise.
- Launch with measurement wired in Analytics, Search Console, and conversion tracking are part of the build, not a follow-up ticket. You can't iterate on what you aren't measuring.
- Iterate over quarters Organic growth is not a launch event. The sites I've grown got there through months of adding pages, fixing what underperformed, and doubling down on what ranked.
Questions
Common questions
Do you work with clients outside Israel?
Yes — most of my work is with US and European clients. I'm a native English speaker (American, University of Maryland), and Israel time zone overlaps a full working morning with Europe and the early afternoon with the US East Coast.
How long until SEO work shows results?
Technical fixes can move rankings in days. Building genuine organic traffic on a new site takes quarters, not weeks — my own sites took months of consistent publishing before traffic became meaningful. Anyone promising you page one in 30 days is selling something else.
Can you take over an existing codebase?
Regularly. A good portion of my professional work has been inheriting half-finished systems and getting them to production — legacy PHP, undocumented WordPress builds, and applications whose original developer is long gone.
Are you available full time or freelance?
Both. I run my own SaaS products and take on select client work alongside them. If you're hiring for a founding or senior engineering role, that conversation is welcome too — my resume is here.
Who owns the code?
You do. Client work ships to your repository, your hosting, your accounts. No proprietary platform lock-in and no hostage situations if you later bring things in-house.