עב

Excel, an old system or a shiny new CRM. Still not working?

floeey maps how work gets done in your business, specifies the right solution for you, and builds it: automation, a CRM, custom software or a mix.

15 minutes. You talk, we mostly ask questions.

  • monday.com partner
  • origami.ms partner
  • make.com partner

Some of our clients, past and present

11+ years of team experience, 60+ projects delivered

  • Weksler Bregman
  • Kishurei Lemida
  • Total Immersion Swimming
  • HaMeamenet
  • Novohealth
  • Campus Siim
  • Supportify
  • Barzilai Design
  • Digital Planet
  • shufizoo
  • AlphaDevs
  • CallMarker
  • Studio 6B
  • Be Home Remodeling
  • Chava Zingboim
  • Beta Estate
  • empty_space
  • TIP
  • Personal Mortgage Consulting
  • Lev Achim VeAchayot

Luck is not a way to run a business.

Every note like this is a step in a process that runs on luck. In the specification we go through them one by one and define three things for each step.

  1. Who owns itEvery step has a role that answers for it.
  2. What triggers itAn event in the system starts the step, without waiting for someone to remember.
  3. What happens when it gets stuckAn alert to the right person, and a fallback route set in advance.

An example: what happens after one WhatsApp message

A customer asks to postpone a delivery. In an automated process, everything that follows runs on its own, and nobody on the team touches it.

  1. WhatsAppIncoming messageCan I move the delivery for order 4821 to Thursday?
  2. The botChecks and answersYes, the order hasn’t shipped yet. I’ve moved it to Thursday, 10 am to 2 pm.
  3. CRMThe record is updated

    The new delivery date is saved in the customer record.

  4. WarehouseThe warehouse knows

    A task opens for the packer, with the new date.

From message to warehouse: one minute. Nobody had to pick up the phone.

It all starts with a specification

Before we build, we map how work gets done: who does what, in which tool, and where it gets stuck. We gather everything and draw the diagrams the process needs. Usually: how the process should run, what data the system holds, and what your customer goes through along the way. It all ends up in one document a team can build from. More about the specification

Our service areas

Most projects combine more than one area. The specification settles which ones are right for your business. See all services

Automation and integrations

We connect the systems you already have, so information moves between them without anyone typing it twice.

  • Processes with conditions, branches and exceptions
  • Documents read and entered automatically
  • When something gets stuck, a person hears about it
Read about automation

Selected projects

Six examples from the 60+ projects we’ve delivered. In each folder: what the client needed and what we built.

More about the projects

Total Immersion Swimming

One organization, three systems

  • A CRM for the whole organization. Customer data migration, a sales call center and academy management.
  • A voice agent. Calls customers and confirms they’re coming.
  • A portal for the coaching team. Connected to the organization’s systems.

CRMVoice agentPortal

A pharma company

Documents processed with no manual entry

  • PDFs are read and entered into the organization’s systems automatically.
  • Employees stopped typing the same data twice.

AutomationPDF

Supportify

A system for a patient support program (PSP)

  • A system that follows the patient through the program, with all the information in one place.

PSPCustom system

Kishurei Lemida

An academy and an assessment clinic in one system

  • Managing the academy and the assessment clinic, without jumping between tools.

Academy managementClinic

HaMeamenet

Sales, leads and a chatbot

  • A CRM for the sales team and the lead funnels.
  • A chatbot that answers and hands off to a rep when needed.

CRMChatbot

Medical equipment importer

From the customer to the accounting document

  • CRM and ERP end to end: customers, orders, purchasing, cash flow and accounting documents.

CRMERP

You walk away from every stage with something in hand

Four stages, from the first call to a running system. Each one ends with something concrete in your hands. More about how we work

  1. An intro call, then we map the process. Lots of questions, including ones nobody has asked you yet.

    You walk away withProcess map

  2. We write down what we’ll build, in which tool, how long it will take and what it will cost. Before we build anything.

    You walk away withA specification document and a fixed quote

  3. We build in stages and test every scenario before your customers run into it.

    You walk away withA working system

  4. We train your team and provide a warranty period after go-live. After that, you can keep us on for support and maintenance.

    You walk away withTraining, documentation and a warranty period

We build voice agents. You can try Menachem now, in Hebrew.

A voice agent makes or answers calls and updates your systems while it talks. We build each one for the calls your team makes every day, in operations and service. One we built calls customers to confirm they’re coming.

Calls a voice agent can handle

  • Attendance confirmation
  • Customer reminders
  • Order status
  • Collecting details
  • First-line support
  • Call routing

In English we also build voice agents for sales.

Menachem, a pink octopus with glasses and a tie, answering the phone and taking notes

Got an API? We’ll connect it. No API? We’ll tell you up front.

Sometimes it’s Make, sometimes it’s code. We choose based on complexity, volume, cost and security.

  • monday
  • Origami
  • Pipedrive
  • HubSpot
  • Salesforce
  • Fireberry
  • Zoho
  • Airtable
  • ClickUp
  • Google Workspace
  • Microsoft 365
  • Dynamics 365
  • Make
  • n8n
  • Zapier
  • Priority
  • SAP
  • NetSuite
  • Hashavshevet
  • iCount
  • Rivhit
  • EZcount
  • Cardcom
  • PayPlus
  • Tranzila
  • SUMIT
  • morning
  • Grow
  • Voicenter
  • Paycall
  • Voipe
  • Reshetkol
  • 019
  • Twilio
  • CallMarker
  • WhatsApp
  • ManyChat
  • UChat
  • Glassix
  • CommBox
  • Intercom
  • Rav Messer
  • smoove
  • ActiveTrail
  • INFORU
  • 019 SMS
  • Contaqt
  • SendGrid
  • Mailgun
  • Shopify
  • WooCommerce
  • WordPress
  • Elementor
  • Webflow
  • Wix
  • LearnDash
  • Zite
  • base44
  • Lovable
  • AWS
  • Google Cloud
  • Vercel
  • ChatGPT
  • Claude
  • Gemini
  • Microsoft Copilot
  • Grok
  • Perplexity
  • ElevenLabs
  • Canva
  • Higgsfield

Most of the systems we support and have worked with at some point.

See all systems

No call center here. You get Michael, Eran, Shir and Dobby.

More about us

We met at work, sharing a role. We’re both product managers and tech people, and we both noticed the same thing: the market is full of solutions, and very few people stop to diagnose the problem.

What good is another pill when what you need is a detox?

So we started floeey to sort things out. We bring our business experience to other businesses, and we build processes and solutions that solve the actual problem, at a quality we don’t compromise on. With a user experience we’d want to use every day ourselves.

Eran and MichaelFounders of floeey

  • We diagnose before we prescribeFirst we find out what’s really stuck. Only then do we decide what to build.
  • We say when it’s not a fitIf we’re not the right people, or what you have is enough, you’ll hear it from us.
  • We build it like it’s oursA system that’s pleasant to work in, because someone will open it every morning.
  • Co-founder and CTOMichael MaorAsks "what for?" before every new tool.
  • Co-founder and product leadEran BraunsteinLooks at the process through the eyes of the person using it.
  • Project managerShir MitzrafiMakes sure things happen on time.
  • Office managerDobbyMakes sure everyone gets out of their chair once an hour.
  • AI assistant and voice agentMenachemCalls to book intro calls and stays with you for as long as you work with us.

A short call, no slide deck. You describe how the business runs today and where it gets stuck, and we ask questions. By the end, it’s clear whether we’re a fit and what the next step is.

It depends on the scope. After the specification you get a fixed quote in writing, before we start building.

It depends. Sometimes replacing a system is the right move, sometimes it’s better to keep what you have and improve the process around it, and sometimes keeping your current systems is a requirement you set up front. In the specification we weigh the cost and benefit of each option and decide together.

It depends on the scope. A focused automation takes less time than a large system. You get a precise timeline in writing after the specification.

You do. We always set everything up so the client owns it: accounts are opened in your name, and we work in them as a user you can remove. At handover you get full access and documentation.

We work in your accounts with minimal permissions, and we don’t ask for access to anything we don’t need.

Almost. If it has an API or another reliable way to get data in and out, we’ll connect it. If it doesn’t, we’ll tell you up front.

Every system has pros and cons, and none fits everyone. In the specification we work out with you which one is right for you, based on the system requirements, costs, language support, data security and more.

There are license fees for the tools themselves. After the warranty period you can buy support and maintenance from us, if you choose.

After go-live there’s a warranty period. After that you can buy support and maintenance from us, or run the system yourselves with the documentation you received.

Yes. The intro call, the specification, the documentation and the support all happen online, so location doesn’t matter.

Want numbers before we talk? Two free calculators, no details required.

How many hours could automation save you?What do WhatsApp messages cost?

One call. And if we’re not the right fit, we’ll say so.

You describe a normal day in the business. We stop you every time someone "just remembers" to do something. After 15 minutes both sides know whether there’s a project here.