Skip to main content
The-Hunters home
+972 3-381-9955Let’s talk

About The-Hunters

We don’t start with technology. We start with what isn’t working in your business.

The-Hunters has been building technology solutions for businesses since 2019. Before we choose a system, a tool or an AI model, we work out what is stuck in the process, what it costs the business, and the simplest reliable way to fix it.

  • Since 2019
  • A family business
  • We design, build and support
Chen Urieli, founder of The-Hunters
Chen UrieliFounder, The-Hunters

Who we are

There are people behind the systems.

Since 2019 we have worked with businesses in many fields. We have connected systems that didn’t talk to each other, built automations, set up customer communication channels and developed complete systems. The tools have changed over the years. What the work has in common hasn’t: a real operational problem that someone in the business feels every day.

The-Hunters is a family business. The people who design your solution get to know your business, and stay available after the system goes live.

Chen Urieli, founder of The-Hunters. Specializes in planning and developing technology solutions tailored to business needs, including system integrations, automation, WhatsApp, custom systems and artificial intelligence.

Chen on LinkedIn

How we think

Technology is the tool. Not the goal.

We don’t add systems, integrations or AI just because we can. Every component in a solution has to earn its place: in what it does for the business, in how reliable it is, and in what it costs over time.

  • We also design what doesn’t need to be built.
  • The simple, reliable solution comes before the impressive one.
  • Monthly running cost is part of the design, not a surprise on the invoice.

Architecture before tools

Problem first. Architecture second. Tools last.

First we understand what isn’t working. Then we design the right process. Only then do we choose the tools, and only the ones that are really needed.

  1. What’s broken today

    1. Request comes in
    2. Copied into Excel (Manual work)
    3. Asked in the group (Manual work)
    4. Checked in two systems (Manual work)
    5. Copied again (Manual work)
    6. Reply to the customer

    One request, many hands.

  2. The right process

    1. Request comes in
    2. Recorded in one place
    3. Reaches the right person
    4. Customer gets an answer

    Fewer steps, no copying.

  3. Only the tools it needs

    1. Request comes inWebsite form
    2. Recorded in one placeCRM
    3. Reaches the right personAutomation
    4. Customer gets an answerWhatsApp

    A tool only where it does a job.

  • Fewer systems
  • Less manual work
  • Less maintenance
  • Lower monthly cost

The same need, two ways

Less complexity. Less maintenance. Less to pay every month.

When you keep adding

Every extra component is another connection, another possible failure and another bill.

Complexity
8 components
Failure points
Many failure points
Monthly cost
High, and grows with every request

When it’s designed

AI in one place only, and everything else simple and predictable.

Complexity
4 components
Failure points
Few failure points
Monthly cost
Low and predictable

The goal isn’t to build the most complex system. It’s to build the right one. Every unnecessary component is another monthly charge, more maintenance and one more place where something can break. A well-designed system costs less every month, breaks less often and is simpler to change.

What it means for the business

  • A low, predictable monthly cost
  • Less maintenance and fewer failures
  • Simple to change and extend

AI in the right place

AI is a component. It isn’t the architecture.

We use AI a lot: to understand free-text requests, to classify, to summarise calls and for Voice AI. Where it adds value, it’s excellent. Where ordinary code does the job, it only adds cost and complexity.

AI at every step4 AI calls per requestCosts more, less predictable
  1. Input
  2. AI (AI component)
  3. AI (AI component)
  4. AI (AI component)
  5. AI (AI component)
  6. Output
AI only where it helps1 AI calls per requestCosts less, predictable and stable
  1. Input
  2. Deterministic processing
  3. API and business rules
  4. Language model (AI component)
  5. Deterministic output

A conceptual diagram. In every project the answer looks different.

In the long run

Today it’s easy to build something that works. It’s much harder to build something that still makes sense to run over time.

AI tools can explain to almost anyone how to build almost anything, and sometimes the result really works. They are great tools. The important decision comes afterwards: what happens after a month, after a year, and when the volume grows.

We have seen processes that could run for a few dollars a month next to alternatives doing the same job for hundreds of dollars a month. The difference wasn’t the tool. It was the design.

The questions we ask before we build

This is how we avoid complexity and costs nobody needs.

  1. What happens when the volume grows tenfold?
  2. What happens when a provider changes its pricing?
  3. What happens when an API stops responding in the middle of the night?
  4. Who maintains this a year from now, and what will they need to know?
  5. What does it cost per month, not just to set up?
  6. Do we really need another system, or can we do without it?

Not more technology. A business process that works better.

Tell us what isn’t working. We’ll look at it with you before anyone talks about tools.

Tell us what isn’t working