What it costs, in one place.

Yes. About twenty minutes on the phone or Zoom. You tell me the problem; I tell you straight whether I can help, how I would do it and roughly what it costs. No card, and no follow-up sequence if the answer is no.

Because they are cheaper to deliver. One sitting means no ramp-up each time and, on-site, one trip instead of several. A full day works out to $188 an hour and a full week to $163, against $225 for a single hour.

The trip costs about as much time as an hour of work, so a single hour in person is poor value for you. Three hours is the shortest visit worth making, and travel is included in NYC, Jersey City, Hoboken, or nearby. Further out I quote the travel. A single hour works well on Zoom.

Regular check-ins while you or your team build: an hour this week, two the next, on Zoom, or drawn down as half days at your desk inside NYC, Jersey City, Hoboken, or nearby. It is $2,000, used within 90 days.

Up front. Sessions are paid before they happen, by card at /booking or on an invoice I send after the call. Larger companies with a purchasing process can be set up on terms; say so on the call. Builds are paid in stages against the written scope.

10% off your first purchase, whether that is an hour, a half day or the pack: mention it on the free call or use code FIRST10 at checkout. Beyond that, the discount is in the sitting: a full day or a week costs less per hour than single hours. The published rates are the same for everyone, however you found me.

With me. I scope it, review it and answer the phone. I use my 30 years of experience to direct other engineers and AI agents (FireControl, the operations layer that runs everything in this portfolio) to deliver the work at team speed without the agency overhead. On larger builds, engineers I have trained through my apprenticeship handle parts of the work under my supervision. I review every commit, and you will know who did what.

Everything I build is documented and in your name, so any competent engineer can pick it up. That is deliberate: at the end of the engagement you hold the keys to your castle. I do not need leverage to get you to come back.

You do, from day one: the code, the cloud account, the domains, the credentials. Nothing is held on my accounts as leverage.

Sessions are by the hour. Once the work is understood well enough to scope, a build is quoted at a fixed price with a written scope, so the risk in my estimate sits with me, not you.

Yes, heavily. It is a large part of why builds take days instead of quarters. Everything goes through the discipline I would apply to hand-written code: review, tests, migrations, backups, and credentials that never pass through a model. Doing that well is also what I teach.

Yes. Building it for you and teaching you to build it are two ends of the same dial, at the same rate. Most clients choose some of each: I build the hard part and your people learn by being in the room.