Guides ·
How long does it take to install AI on your own premises?
A typical Seesa installation is working within approximately 30 days of agreement. That is a typical figure, not a promise: the schedule is confirmed after Seesa assesses your hardware, your systems and your data, and installation timing is set out in your proposal. The time depends less on the machine than on how many systems you want to connect and how much history you want to bring in.
The short answer
Seesa’s on-premise page says it aims to have Seesa working within approximately 30 days of agreement. Standard setup is included: installation, historical import, supported system connections and permission configuration. Your proposal describes the scope before you order, so you know what is part of setup and what would need bespoke work.
Stage one: understand your setup
Before anything is installed, Seesa looks at how many people will use it, what it will do, which systems it will connect to and how much history it needs to hold. These answers drive everything else, including the hardware.
This is also when you choose how to arrange the hardware: buy it, lease it over 24, 36 or 48 months, or share the specifications of suitable hardware you already own so that it can be checked against your workload.
Stage two: prepare and install
Next, the hardware and site requirements are agreed and Seesa is installed on your premises. Your team provides the access needed for the systems you want to connect.
In practice, this is where your side of the work matters. Seesa’s on-premise page lists three things your team provides:
- A suitable location, power and network access for the agreed hardware.
- People who can authorise the system connections you want to use.
- Someone who can help agree permissions and check the first workflows.
Stage three: build your company memory
Once the installation is in place, the agreed history is imported, permissions are configured and connected sources are checked. This is what turns a working machine into something that can answer questions about your company: it builds one memory from your records, with the right access for each person.
Your team can also add and manage supported connections through settings, so the work does not end at go-live.
Stage four: put it to work
Your team starts asking questions and using routines. Pentatonic manages supplied installations, and bespoke workflows can be scoped separately with specialists. Before the installation goes live, the support connection, permissions and data-access arrangements are documented for your deployment.
What can make it faster or slower
Seesa does not publish a formula, but the on-premise page names the factors that shape the installation. People, history, simultaneous use and the work Seesa will do affect it, and storage and processing capacity are assessed together before hardware is recommended. The page says the schedule is confirmed after assessing your hardware, systems and data.
From a practical point of view, a few things are within your control:
- How quickly the location, power and network access are ready.
- How quickly someone can authorise the connections to your systems.
- How clear you are about which systems and how much history to include.
- Whether a system needs a bespoke connection. For a CRM, ERP or specialist record system, Seesa assesses the connection or import route before you order, and bespoke work is agreed first.
Why the hardware is not a quick purchase
An AI system needs a machine with enough graphics processing units (GPUs) and memory to run the models quickly for everyone who uses it at once, plus enough storage for your records. Choosing it is a sizing exercise rather than a catalogue order. Seesa assesses storage and processing capacity together, and verifies latency and concurrency before proposing hardware, which is why the first stage is spent understanding your setup.
If you are using hardware you already own, the check runs the other way: you share its specifications, and Pentatonic checks it against your workload before agreeing the installation and support arrangements.
Settle these before you agree
The 30 days is counted from agreement, so the useful work happens before it. Your proposal sets out the scope, the hardware arrangement, the costs and the installation timing. If you plan to lease, the website terms note that a 24, 36 or 48-month lease is subject to financing and a signed agreement.
- Where will the machine live, and is power and network access available there?
- Who will authorise each system connection, and do they know it is coming?
- Who will agree the permissions, and who will check the first workflows?
- Is there a system that will need a bespoke connection, and has that been scoped?
What happens after the first month
Installation is the start of the relationship, not the end of it. Pentatonic manages configuration, software updates and maintenance for the systems it supplies. If you later want help turning a particular process into a routine, optional specialist engagements are available and priced separately.
To talk through your own timescale, start with the on-premise page and then tell us where you are based, how many people will use Seesa and what you want to connect.
Questions, answered.
How soon can we use Seesa?
A typical installation is working within approximately 30 days of agreement. The schedule is confirmed after assessing your hardware, systems and data.
Do we need to buy hardware first?
No. You can buy it, lease it over 24, 36 or 48 months, or ask Pentatonic to assess hardware you already have.
What do we need to provide?
A suitable location, power and network access for the agreed hardware; people who can authorise the connections you want; and someone to help agree permissions and check the first workflows.