Skip to content
ivisionAI

FAQ

Questions people ask before they start

The questions that come up in almost every first call, answered the way we'd answer them on the call. If yours isn't here, ask us directly — we'd rather have the awkward conversation early.

What you get

What exactly does divisionAI build?
One AI-powered business management system, tailor-made to your processes. In practice that means custom CRM and ERP-style modules — sales, projects, inventory, finance, HR and whatever else your operation needs — under one login, with AI agents running the repetitive work inside it. It replaces the scattered tools your team currently moves data between rather than adding another one to the pile.
Is this a product I subscribe to, or something built for us?
Built for you. There's no shared multi-tenant product you're renting a seat in. We build one system around your processes, and you own the result — code and data both. That's a deliberate difference from SaaS: leaving us doesn't mean losing your system.
How is this different from hiring a normal development agency?
Mostly speed and what you're billed for. Our AI workflows generate the bulk of the code while senior engineers own the business logic, the security model and the data migration. That's what compresses builds that would traditionally take months into weeks — and we bill for the scope delivered, not the hours spent delivering it.
Do we have to replace everything at once?
No, and you shouldn't. We sequence the build so the highest-pain area goes live first and the rest follows in phases. Old and new usually run in parallel for a period, deliberately. Big-bang cutovers are how consolidation projects fail.

Cost and timing

What does it cost?
Pricing is by scope, not by seat or by hour. Three tiers exist — Small (a few core modules for one focused team), Medium (six to eight modules across several departments, the typical business), and Enterprise (the full suite with deep agentic automation). Which tier fits is usually clear within one conversation, and you get a fixed number for the scope rather than an hourly estimate that drifts.
Why don't you publish prices?
Because the honest answer depends on scope, and a published number would either be misleadingly low or scare off businesses it would actually fit. We give you a real figure after discovery, before you commit to the build.
How long until something is actually running?
First working modules are typically live within weeks. Our agency CRM case study went from start to a unified system in four weeks — work a conventional build would have spread over about eight months. Full multi-department suites take longer, but you see working software early rather than at the end.
Are there per-user fees as we grow?
No. Adding people to your own system doesn't cost you a licence, which is a large part of why consolidating off a per-seat SaaS stack pays for itself. Ongoing costs are hosting plus whatever support arrangement you want.

Data, risk and ownership

Who owns the code and the data?
You do, outright. The code is yours to keep, host and modify, and the data lives in your system rather than in someone else's multi-tenant database. If you ever want another team to take over, you can hand it to them.
What happens to the data in our current tools?
It gets migrated. The data layer phase exists for exactly this: we clean, deduplicate and load your existing records so the new system launches with your history intact. Deduplication usually surfaces things worth knowing — the same customer under four spellings is the normal starting condition, not an unusual one.
Is our data used to train AI models?
No. Your business data is not training material. AI agents operate on your data to do work inside your system; that's a different thing from contributing it to a model.
What if an AI agent gets something wrong?
Agents run inside explicit boundaries decided during the build — what they can do on their own, what they must propose for human approval, and what they can never touch. Most agent work is drafting and proposing rather than committing: the agent prepares the purchase order or the report, a person approves it. Anything with real consequences keeps a human in the loop by design.

Working with us

Where are you based, and does that matter?
Global-remote with European hubs in Tirana and Cologne. In practice it matters for timezone overlap and for being reachable — the SLA is a reply within 24 hours.
What do you need from us during the build?
Access to the people who actually do the work. Discovery depends on watching real processes rather than reading a process document, because the two rarely match. Expect a meaningful time commitment from a few key people early, tapering sharply once the map is agreed.
What if we already have software that works?
Keep it. If a tool genuinely earns its place we integrate rather than replace — the goal is removing the copy-paste between systems, not migration for its own sake. We'll tell you if we think a standard product fits your case better than a custom build; that answer is sometimes the right one.
How do we start?
A 30-minute call. We map roughly where your processes are bleeding, tell you whether this is a fit, and give you a straight answer on scope and cost. No deck required.

NEXT STEP

See what this looks like for your business.

A 30-minute call, a map of your processes, and a straight answer on what a tailor-made system would cost you. No deck, no pressure.

OPERATIONS

  • Operations: Global Remote
  • European Hubs: Tirana / Cologne
  • SLA: Reply < 24 Hours