Frequently asked questions
52 short questions and answers, by topic. If yours is not here, a 15-minute intro call will answer it.
The process: intro call, specification, build, handover and support
We start by understanding how the business works, and from there we choose tools and build. The stages are an intro call, specification, build and testing, and support with a warranty period. At each stage it is clear what you get and what we expect from you.
A short call with no slide deck and no commitment. We hear how the business runs today, where things get stuck, and which systems you already have. At the end you know whether we are a fit and what the next step is.
The specification does more than record what exists. We map the process, ask why it works that way, and simplify where we can. At the end you get a written specification and a fixed quote, before any building starts.
Michael Maor, co-founder and CTO, leads every specification. Eran Braunstein, co-founder and product lead, joins on product, marketing and user experience.
After you approve the specification and the quote in writing. We do not start building before we agree on the process, the scope of work and what counts as done.
You get a working system, documentation of every process, and training for the team that uses it. We always set everything up under the client’s ownership, so the accounts and access are yours from day one.
There is a warranty period after go-live, during which we handle fixes. After it you can choose to continue with our support and maintenance services.
We build with documentation and alerts, so a fault shows up early. Fixes during the warranty period are on us. After it they are handled under the support and maintenance services, if you chose them.
The agency: who we are and who you work with
floeey is an agency that specifies and builds processes and systems for businesses. Michael Maor and Eran Braunstein founded it, and both are product managers and technology people. We build automations, CRM systems, integrations between systems, portals and voice agents.
We start with a diagnosis before choosing any tool, and we are not tied to one platform. One team works with you from specification to code. If we are not the right fit, we will tell you.
Growing businesses that have a team, recurring processes and systems that do not talk to each other.
Yes. We work with clients worldwide. The intro call, specification, documentation and support all happen online.
Michael Maor, co-founder and CTO, leads every specification. Eran, developers, integration specialists and designers join as needed.
floeey, in lowercase. That is how the agency name is written. There are similar names on the market, such as Flowi and Flowy, and we have no connection to them.
Yes. Portals, customer interfaces, dashboards and internal apps, when an off-the-shelf tool is not enough. We first check whether what you already have can solve it. If it cannot, we develop only as much as is needed.
Where you are today: Excel, WhatsApp and scattered tools
Yes. Many businesses start there. We map how the work runs today, then build order and connections at a pace that suits you. You do not need to buy a new tool just because everyone else has one.
We start by understanding which information needs to move between the tools. Sometimes connecting them is enough, and sometimes replacing one of them is the right call. We weigh the cost against the benefit of each option.
Yes. We check why it is not used: the process is unclear, a connection is missing, or the tool does not fit. Based on that, we decide whether to improve what you have or move to another tool.
When a process repeats, when someone moves information between systems by hand, or when the team spends hours copying. If the business is growing and the manual work grows with it, it is a good time to map the process.
It depends on the case. Sometimes replacing a system is the right move. Sometimes it is better to keep what you have and improve the process around it. And sometimes keeping the current systems is a requirement you set from the start. In the specification we weigh the cost against the benefit of each option, and decide together.
Of course. The questions are whether the process itself is right, and whether the connection will be clear and easy to maintain day to day. We answer those in the first call.
Costs
It depends on the scope. After the specification you get a fixed quote in writing, before we start building.
We work with a fixed quote for the agreed scope, so you know what is included before we start. Large changes in scope go through a written update.
The agreed scope: specification or build, the integrations, the testing and the handover, as written in the quote. Anything outside the scope is priced separately and openly.
There are the licenses of the tools themselves. After the warranty period you can buy support and maintenance services from us, if you choose to.
Choosing systems
Every system has pros and cons, and none fits everyone. In the specification we work out with you which solution is right for you, based on the system requirements, costs, language support, information security and more.
Both are good automation tools. The choice depends on complexity, run volume, cost, security and who will maintain it after handover. We pick what fits the process.
By the process. We look at how a lead comes in, how you follow up on it, which systems you already have, what the costs are and how well the tool supports your language. Sometimes you stay with what you have and improve it. Sometimes we recommend another tool, and explain why.
Almost. If it has an API or another orderly way to get information in and out, we will connect it. If it does not, we will tell you up front.
Yes. We start with a version that works and add to it gradually, instead of building everything up front.
Preparing: the intro call and the specification
There is no heavy homework. It is enough to think of one recurring, frustrating process and the tools you already use. If you have an example, such as a spreadsheet, a screenshot or a short description, that helps, but it is not required.
Someone who knows the day-to-day work, not only the view from the top. Useful things to bring: a description of the process, the tools in use, and an example of a lead or an order that goes through by hand today.
The intro call is short. The specification takes a few focused conversations with whoever knows the process, so we do not specify by guessing. The build itself happens on our side, with checkpoints for your approval.
AI and voice agents, security, schedules and maintenance
Automation connects fixed steps: a lead comes in, gets saved, a message goes out. An AI agent or a voice agent comes in when the job needs conversation, understanding or a reply in free language, for example on the phone or on WhatsApp. Sometimes you need only the first, and sometimes the combination.
Menachem is floeey’s voice agent, and also the assistant you meet while working with us. He is one example. Sales calls to an Israeli audience in Hebrew are a weaker fit for a voice agent, so in Hebrew we focus on operations and service, such as confirming attendance, reminders and status checks. In English we also build voice agents for sales.
We work in your accounts, with minimal permissions, and we do not ask for access to anything we do not need.
On the website we collect only what we need to get back to you, according to the privacy policy and the cookie policy. End-customer data is processed in your systems and those of the agreed vendors, with data processing agreements where needed.
It depends on the scope. A focused automation takes less time than a broad system. You get an exact schedule in writing after the specification.
After go-live there is a warranty period. After it you can buy support and maintenance services from us, or run the system yourselves with the documentation you received.
Choosing a vendor: general questions
Check how they start (mapping before building), whose name the accounts will be opened in, what documentation you get at handover, what support and availability look like after go-live, and what the price includes compared with the tool licenses. It also helps to hear about similar projects, and to see that you can start with one clear process. A checklist beats a gut feeling.
For example: what is delivered in writing at the end of the specification or the setup, who will actually work on the project, what support includes and what is priced as a change, and whose name the accounts and API keys are in. Also ask what a handover with documentation looks like, and how you continue if you want to operate the system yourselves or with another provider. Clear answers in writing matter more than a general promise.
Ask about cumulative experience and a list of similar projects, and look beyond the founding year. Check who worked on previous projects and whether they are still available, what happens if someone is unavailable during the project or after it, and what support and response hours look like over time. A stable vendor can explain continuity, backup within the team, and documentation that lets work continue when one person is on vacation.
No-code and low-code tools fit clear connections and processes, when you want to move fast and let people who are not developers maintain things. Custom code fits when the logic is complex, when volume or security call for precise control, or when no off-the-shelf tool covers the process. Sometimes the two are combined: orchestration in a visual tool, and heavy logic in code. The process decides.
You do. We always set everything up under the client’s ownership: the 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.
A good specification describes the business goal, the process including exceptions, roles and permissions, the systems to connect and the direction information flows, and what goes into the first version and what waits for the next stage. It also says how you know the work is done, with clear acceptance scenarios. Without this document it is hard to compare quotes or measure success.
Look at a recurring process: how long it takes, how many times a week, and what that time costs over a year. Add recurring mistakes or follow-ups that get missed, and subtract setup cost, licenses and maintenance. If the return looks reasonable for one clear process, start with it. Run the calculation on your own business’s numbers.
Yes. We start by mapping and documenting what already runs: the accounts, the connections and the existing processes. Even if the previous vendor is unavailable, or there is no orderly documentation, it is usually possible to reconstruct the picture, stabilize what needs it, and then keep improving.
No single system fits everyone. Each one, whether monday, HubSpot, Pipedrive, Origami or Salesforce, has pros and cons. The choice depends on the process, the language, the integrations you need (for example WhatsApp or invoicing), the costs and the size of the team. In the specification we write down how you work today, and choose based on that.
Not always. If one person handles a few inquiries and tracks them neatly in a spreadsheet, that can be enough. A CRM becomes useful when inquiries come from several sources, when more than one person handles them, or when you need shared history and a reminder for the next step. Define the process first, then decide whether you need a dedicated tool.
Plan in advance for documentation, alerts, and who is responsible when a change or a fix is needed. Tool licenses are separate from vendor support, and you can choose ongoing support or in-house operation with a clear handover. A live system changes with the business, so agree on a route for updates as well as a launch day.
Yes, and it is usually a good way to start. Pick one clear process, measure it, and learn how the joint work runs before expanding. A large project fits once there is a specification and agreement on scope. It does not have to be the first step.
Going live is only part of it. The team uses the system for the agreed process: inquiries come in, each has an owner and a next step, and the agreed integrations work. A success measure written in advance, such as lead response time or the end of manual copying, helps more than a general sense that everything is up.
No question matches this search. Try another word, or book a call and we will answer.
Want numbers before we talk? Two free calculators, no details required.
Still have a question? Ask us directly.
15 minutes. You talk, we mostly ask questions.
