EYAL GANTZ

I build software that takes repetitive work off a business: reading supplier PDFs, routing requests, keeping inventory and records in sync. I also build custom Laravel apps and Shopify stores, and I work as a fractional CTO for companies that need one senior technical owner. I write the code myself, set it up in accounts you own, and keep it running after launch. I have built software since 2003, shipped more than 100 products, and was a founding-team engineer on Spot, which NetApp acquired in 2020.

The first step is a free 15-minute call. Most engagements start with a sprint from $7,500. If it proves out, a pilot at $25,000, then a retainer at $5,000 a month. Store owners start with a $3,500 audit, credited in full toward the build. Every step is a fixed price agreed before work starts. No hourly billing.

Most projects run 4 to 12 weeks from kickoff to production. A focused MVP can ship in 3 to 4 weeks, an e-commerce build with catalog work and integrations typically takes 6 to 10, and a larger platform with multiple systems involved can run a quarter or more. Two things keep my timelines honest. First, I work in focused sprints with something reviewable at the end of every week, so you see real progress instead of status reports. Second, there is no coordination overhead: no agency queue, no handoffs between departments, no waiting on another team's sprint to end. The estimate I give you up front is one I have hit many times before, and if anything threatens it (a third-party API, a scope change, a surprise mid-build discovery), you hear about it the day I find out, not at the deadline.

Yes, as a flat $5,000 a month retainer. I own the architecture, infrastructure, vendor decisions, security and the roadmap, the way a technical partner would, and I write the code that backs it up. In practice it looks like this: I audit what you have, fix what is fragile, set a roadmap tied to actual business goals, and then run the technical side month to month, shipping improvements myself rather than advising from a slide deck. Because I still write code every day, the strategy stays grounded in what is actually buildable. If you already have developers, I lead them; if you do not, I build it myself. It starts with a free 15-minute call.

An agency sends a salesperson, then a junior. It sells you a team: an account manager who relays messages, a project manager who schedules them, and developers you never meet. Every layer adds cost, delay, and translation loss. With me, the person on the first call is the same person who designs the product, writes the code, configures the infrastructure, and picks up the phone when something breaks. 23 years in, one person is accountable for the whole job: me. The trade-off is honest: I keep a limited number of engagements at once, and I say no when the fit is wrong. If your project needs a fifty-person organization, I will tell you that on day one and point you to one.

I am one person, and I say so. What protects you: everything runs in accounts you own, each system ships with a written runbook and a recorded walkthrough, and the code is conventional Laravel that any competent developer can take over. I do not currently have a contracted backup developer, so for anything business critical we agree in writing, before the build starts, what happens if I am out for two weeks. I also take one pilot at a time, which keeps a live client from competing with a new one for the same hours.

I live and work in New York City, with clients across the United States and Israel, in English and Hebrew. Most engagements run entirely remote: async updates, short focused calls, and demos of working software instead of slide decks. Time zones are rarely a problem; I have run projects with US teams by day and Israeli teams by evening for years. For clients in the New York area I am happy to meet in person for kickoffs, architecture workshops, or a working session when a whiteboard genuinely beats a screen share. The bilingual part is more useful than it sounds: I have built and shipped fully bilingual English-Hebrew products, right-to-left layouts included, and can work directly with Israeli vendors, teams, and stakeholders without anything getting lost in translation on either side of the ocean.

Yes, and I have the receipts: I was a founding-team engineer on Spot, which NetApp acquired in 2020. Startup work has its own physics: the budget is finite, the direction changes, and speed matters more than polish in the right places. So I build MVPs that are deliberately small but structurally sound, meaning the version that finds product-market fit does not have to be thrown away and rebuilt. If you are pre-funding, say so up front; I would rather point you at a scrappier path today and work together when the timing is actually right.

You do. Everything I build lives in accounts you own: your GitHub repository, your AWS or Laravel Cloud account, your Shopify store, your domain registrar. I work inside them rather than holding anything in mine, so when an engagement ends there is no hostage negotiation, because you were holding the keys the whole time. The code itself is written to be inherited: conventional Laravel, tests, and documentation, so any competent developer can take over without me in the room. There is no lock-in by obscurity either: no proprietary framework, no undocumented magic, no tooling only I can run. Clients stay for years because the work keeps earning its place. If you have been burned by an agency that owned your repo, your hosting, and effectively your business, this is deliberately the opposite model.

It acts on its own for the repetitive, low-risk parts and stops for a person on the rest. Reading a supplier PDF, drafting a reply, matching a record, and filing a document run without anyone clicking. Anything with a price, a promise, or a write to inventory or a ledger waits in an approval queue for a person you name, and nothing changes until they approve. Every read, decision, and approval is logged in your database, so you can see what the software did and why. One setting pauses it without touching your other systems. I do not build support chatbots that answer customers unsupervised, and I do not build systems where a model makes lending, medical, legal, or hiring decisions. When the software is wrong, you are the one responsible for the result, so the person who is responsible should be the one who approves.

It stays in accounts you own. The code repository, hosting, database, and logs are opened in your name, and I am added as a user. Calls to Claude or OpenAI run through an API account in your name, so that provider's retention and training terms apply to you directly and you can read them yourself. Each step sends the model only the fields it needs, not the whole record. Each system gets its own scoped key, kept in your hosting environment rather than in the code. I do not have a SOC 2 report, and I do not keep a contracted backup developer on retainer, which the security page says plainly. If your work carries client-confidentiality duties, we review the data flow for your specific system during the architecture sprint, before anything is built.

Every project includes a stabilization window after go-live where I monitor production, fix what surfaces, and tune performance against real traffic instead of assumptions. After that, most clients keep the retainer, $5,000 a month, which covers monitoring, security patches, dependency updates, verified backups and improvements, so the product keeps compounding instead of quietly rotting. Some clients prefer to come back project by project; that works too, and the codebase is documented so nothing depends on my memory. What I do not do is disappear after the final invoice clears. Several of my longest engagements, including ones you can read in the case studies, started as a single build and turned into multi-year technical partnerships, because the cheapest feature you will ever ship is the one added to a healthy, maintained codebase.

Send a note through the form with what you run and roughly when. If it's a fit, I reply within one business day to set up a free 15-minute call, then send a fixed price for the first paid step. If it isn't, I'll point you somewhere better. Two or three plain paragraphs beat a formal brief. I keep a limited number of engagements running at once, so lead time depends on the current queue. There is no cost to the conversation, and I do not chase.