Skip to main content
Free 15-minute call first. Fixed prices after. See prices

For firms and brands where a wrong answer is expensive

No request waits in the wrong inbox.

I build the hand-offs between your people and your tools: routing, reminders and escalations that follow rules you approve. Approvals, and anything the rules do not cover, go to a person.

I'm Eyal Gantz, one senior developer in New York, and I've been building software for 23 years. I've also been the AI and automation engineer for Salem Wine & Liquor since May 2026. Read the case study on eyalgantz.com.

Then a $950 review, credited toward the build. For the first five clients, the Build balance is due only when it's live.

Example feed. Not a customer record.

A stalled approval, noticed and escalated

  • Form

    New vendor request submitted, contract attached

  • AI

    Read it and routed it to the contract reviewer

  • Timer

    Reviewer has not opened it. Reminder sent

  • AI

    Past the limit you set. Summarized and escalated to you

  • You

    You approve it or hand it to someone else.

Where hand-offs stall today.

  • Nobody knows whose turn it is

    The request was forwarded twice. Each person thinks the other one has it.

  • Approvals sit unseen

    The approver is traveling, the email is buried, and a client's start date moves because of one signature.

  • The odd case breaks the process

    A request that fits no category gets parked, and nobody is told it is waiting.

What I build

Rules you agree to in writing, running between the tools you already have, with a person on every exception.

  • Routing by rule

    AI reads each request, including free text and attachments, and sends it to the right person by type, client and office. The owner is recorded on the request.

  • Reminders and escalations on a clock

    You set how long each step may wait. The owner is reminded before the limit, and past it the request moves to the backup you chose.

  • Approvals with a trail

    Approve or send back in one click from email, Slack or Teams. Who approved what, and when, is kept on the request.

  • The steps in between

    Creating the folder, opening the ticket, copying the details into the next tool. These run without anyone retyping them.

  • Exceptions go to a person

    A request the rules do not cover is never forced into a category. It goes to a named person with the reason it was flagged.

  • One list of what is waiting

    Every open request with its owner, its current step and how long it has been there.

Works with what you already use

  • Slack
  • Microsoft Teams
  • Google Workspace
  • Microsoft 365
  • Asana
  • monday.com
  • Jira
  • DocuSign
  • Zapier

Every request has an owner and a clock.

Requests arrive from forms, email, chat and your ticket tool. Each one shows who has it and how long it has waited.

See prices

Fixed prices. Stop after any step.

Written scope, nothing locked in. Every step stands on its own.

Step 1

Review

$950

After a free 15-minute call: a 60-minute session and a written plan for your top three jobs, each priced. You bring the workflow. No logins, no client or customer data. Credited toward the build within 30 days.

Step 2

Build

from $4,500

One job, built to a written scope at a price fixed before I start, and switched on only when you say. Every account stays in your name, and a handover doc ships with it, so any developer can take it over.

Step 3

Run

from $1,200 /mo

Month to month, cancel any time. I monitor it, fix it, keep the wording and source documents current, and go through the logs with you monthly. AI and hosting fees are billed to accounts in your name at the provider's own price, so there is nothing for me to mark up.

Separate quote

Software

from $15,000

Your own internal tool, client portal or Shopify app, when one Build is not enough. Quoted after the review. Larger platforms are scoped with me directly at eyalgantz.com.

These prices cover one workflow inside the tools you already use. Work that spans a whole store, a custom platform, or the technical side of a company is quoted with me directly at eyalgantz.com, where it starts with a $3,500 store audit or a sprint from $7,500. The first step is the same free 15-minute call.

Ask for a free 15-minute call

If it fits, the $950 review comes next, credited toward the build.

Questions I get on the first call

What runs on its own, and what waits for a person?

Routing, reminders, escalations and the copying between tools follow rules you approved at setup. Approvals, exceptions and anything with a price or a promise wait for a person you name.

What happens to a request that fits none of the rules?

It goes to a person, with a note saying why it was flagged. I do not build a catch-all that quietly files it somewhere.

Do we have to replace the tools we use now?

No. I build between the tools you have: your forms, email, chat and task board. I suggest a new one only when a step has nowhere to live.

Can we change the rules ourselves later?

Yes. The rules are written in plain words in the handover doc, and the common ones (who approves what, how long a step may wait) are built as settings you can edit.

Is this Zapier, or custom code?

Whichever fits. Simple hand-offs can run in a tool like Zapier or Make, in an account in your name. When the logic or the audit trail needs more, I write it as code and document it.

Tell me which hand-off keeps stalling. I'll map the fix.

  • First. I read it myself and write back with a time for a free 15-minute call. Keep it general. No client or customer data needed.
  • On the call. We find the one job worth building. No charge.
  • After. If it fits, the review: 60 minutes and a written plan for your top three jobs. $950, credited toward the build within 30 days. You decide what, if anything, to build.

I reply within one business day.

Ask for a free 15-minute call