Frequently asked questions

Understand GE2Smart before discussing a project.

Pricing, timelines, security, data, spreadsheets, CRM, ITSM or AI: these public answers also power the site assistant.

01

Project and scope

Do we need a detailed specification before starting?

No. A process description, file, screenshot or short conversation is enough for a first reading. The useful scope is clarified before a build commitment.

How do you decide what to build first?

We look at the user journey, the business risk, the value of removing the friction and the smallest scope that can be tested in real conditions.

Can you extend software we already use?

Often. A focused portal, workflow, dashboard, integration or assistant may be more appropriate than replacing a platform that already does most of the job.

Can the first version stay small?

Yes. A small but meaningful first scope is easier to validate, deploy and improve than a long list of speculative features.

02

Pricing, timelines and evolution

What budget should we expect?

Indicative euro ranges start around €1,500–€3,000 excl. VAT for a very focused pilot, €3,500–€8,000 for an operational first version, and from €8,000 for a more structuring first lot. Swiss projects are quoted separately in CHF.

How long does a project take?

Timing depends on scope, decisions, data, integrations, testing and availability of the users. A visible prototype is used to reduce uncertainty early.

Are hosting, licences and integrations included?

They are identified and priced according to the project. They are not hidden inside a generic promise.

Can the tool evolve after launch?

Yes. The first release is designed as a useful operating scope, with decisions about data, access and integrations that allow sensible evolution.

03

Data, security and integrations

Where will our data be hosted?

Hosting is selected during framing according to data, location, availability, security, budget and the operating model.

Can we recover our data later?

Export formats, documentation, dependencies and handover conditions should be specified before the tool becomes critical.

Can you connect to our CRM, ERP or ITSM platform?

Possibly. APIs, exports, permissions, licences, source-of-truth rules and failure handling are checked before the connection is promised.

Is sensitive information needed for a first conversation?

No. A first reading can start with a description of the process. Sensitive files can be exchanged later through an appropriate channel if needed.

04

AI and ITSM

Can an AI copilot use our internal knowledge?

Yes, when the source corpus, permissions, retention and responsibilities are defined. The assistant must not expose information outside the user’s access.

Will AI make operational decisions by itself?

Sensitive decisions and external actions should remain explicitly validated. The exact guardrails are part of the use case design.

Can you help structure a Service Desk?

Yes. The scope can cover intake, incidents, requests, queues, priorities, SLAs, escalations, knowledge, assets, reporting and targeted integrations.

Do you replace ServiceNow, EasyVista or Jira Service Management?

Not by default. A focused extension, portal, workflow, cockpit or assistant may be the right complement to the existing platform.

Your question is specific

Show us the process.
We will answer with a real case.

Describe the process and mention any files or screenshots you could share during a later secure exchange.

Describe my process →
Prendre rendez-vous Horaire à confirmer