STUDIO X

Central X

You have the systems. The overview is missing.

Most businesses already have the systems they need. The problem is that they do not talk to each other. People move information by hand, nobody sees the whole picture, and AI delivers less than you hoped. We develop Central X, the core that connects your systems and makes AI useful, for businesses, organisations and municipalities.

AI does little until your data is connected.

AI does little as long as your data is scattered across email, spreadsheets and line-of-business systems. An AI assistant can only answer from what it can access. Central X brings together the information from the systems you already use, so AI can work on your own data, with control over what it sees and does.

AI only sees what it can access

Many have rolled out Copilot or ChatGPT and see little effect in daily work. Usually the model is not the problem. The information it needs sits in five different systems.

One core, many AI tasks

Once the information is connected, the same core can interpret documents, answer questions about your own data, draft replies and flag what slips. You start with one task, automate it step by step and add more.

Control and privacy first

You decide what AI can see and do, and everything it does is logged. We agree which AI services are used and where data is processed before anything goes live. Data is stored in the EU/EEA.

For businesses, organisations and municipalities

Businesses

Jobs, customers, hours and invoice data in one picture, with AI doing the groundwork.

Organisations

Members, cases, documents and knowledge in one place, so nothing depends on the right person being at work.

Municipalities

Cases and information across line-of-business systems, with AI that interprets enquiries and drafts replies. We know the public sector requirements from apps we have developed for Oslo and Øygarden municipalities, among others.

Recognise three or more?

Then there is usually more to gain than you think. It does not mean anything is wrong. The routines work, people know their jobs, and the work gets delivered. But much of the capacity goes into moving information between spreadsheets, email and line-of-business systems.

  • Customers call to ask about status, and people spend hours answering.

  • The same information is entered several times, by several people.

  • Documentation is scattered across folders, email and phones.

  • Completed work and materials do not always make it into the invoice data.

  • Your systems do not talk to each other, so someone moves data by hand.

  • You have rolled out AI tools, but see little effect in daily work.

Keep what you have. Get one overview on top.

The core pulls data from the systems you already use, where they offer an API. You choose how much it should do, and how much should still be approved by a person.

WHAT YOU HAVEWHAT WE DEVELOPWHAT YOU GETStays as it is today.Pulls data via API. You choose how much it does.One overview that keeps itself up to date.SharePointDocuments, reports and folders.Accounting and hoursTripletex, Visma, PowerOffice.Email and calendarMicrosoft 365, Google Workspace.CRM and salesHubSpot, Pipedrive, SuperOffice.Other systemsAnything with an API can connect.Business systems, databases, portals.Central XGathers what already exists.Keeps the overview current.Suggests the next step.The core starts simple, and growsat the pace you choose.Who is where, on whatPeople, jobs, status and workload.One shared timelineShort jobs and projects in one place.Alerts when work is readyOr when a case stalls for too long.AutomationYou decide the level of automation.Pick up where others left offAll history and dialogue sit withthe job, not with one person.Requires an API or MCP with read and write access.CONTROLAutomationYou decide what needs a yes, and what runs by itself.Everything is traceableWho did what, when, and where the figure came from.Roles and accessYou set the roles. Access follows the user.WHAT YOU HAVEStays as it is today.SharePointDocuments, reportsand project folders.Accounting and hoursTripletex, Visma,PowerOffice.Email and calendarMicrosoft 365,Google Workspace.CRM and salesHubSpot, Pipedrive,SuperOffice.Other systemsAnything with an API. Databases, portals and more.Requires an API or MCP with read and write access.WHAT WE DEVELOPPulls data via API. You choose how much it does.Central XGathers what already exists.Keeps the overview current.Suggests the next step.The core starts simple, and growsat the pace you choose.WHAT YOU GETOne overview that keeps itself up to date.Who is where, on whatPeople, jobs, statusand workload.One shared timelineShort jobs andprojects in one place.Alerts on changesOr when a case stallsfor too long.AutomationYou decide the levelof automation.Pick up where others left offHistory and dialogue sit with the job, not one person.CONTROLAutomationYou choose what needs a yes, and what does not.Everything is traceableWho did what, when, and where the figure came from.Roles and accessYou set the roles. Access follows the user.

There are three levels.

Most start at level one and move up as they see what it delivers. You do not need to decide now how far it should go.

01

Connect what you have

Your systems stay as they are today. We develop a layer on top that pulls in data and keeps the overview up to date. The lowest threshold, the fastest effect, and you do not replace anything that works.

A fit when the systems themselves are good enough, but nobody sees the whole picture.

02

Connect, and fill the gaps

The same core, but we also develop what is missing entirely. Often a mobile view for people out on jobs, digital forms, or invoice data compiled automatically from the entries.

A fit when parts of the workflow lack a system.

03

Bring it into one system over time

The core grows module by module, and gradually takes over tasks that today sit in separate tools for project management, tasks and internal communication. You decide the pace, and how far it should go.

A fit when you pay for many tools that each solve one piece.

How the working day changes.

Comparison of the workflow before and after a core system
TodayWith a core
Customers call to hear where their case standsCustomers log in and see status, documents and progress themselves
Forms on paper and in PDFDigital forms filled in where the work is done
Invoice data is put together afterwardsThe invoice data is compiled from entries along the way
Documents in several versionsOne source, with history per customer, project or unit
Manual keying of incoming email and PDFsAI interprets the content, a person approves
No combined overviewReal-time status for management
Everything sits in the heads of a few peopleThe knowledge sits in the system, and follows the job

AI does the groundwork. You make the decisions.

AI is most useful when it has access to combined, up-to-date information. In the core, it does. We start with AI suggesting and a person approving, and you decide when more can run automatically.

Interprets incoming documents

Emails, PDFs, orders and invoices are read and turned into suggested entries. A person checks and approves, instead of typing everything in themselves.

Answers questions about your own data

“What was agreed with the customer in March?” The core answers and shows where the answer comes from. Knowledge no longer depends on the right person being at work.

Drafts status updates and replies

Status reports for management, and replies to customers wondering where their case stands, are drafted from the data in the core. Someone reads them through and sends them.

Turns speech into entries

The person out on a job dictates on their phone. AI fills in the form, and the person confirms before it is saved.

Flags when something slips

The core alerts you when a case has stalled, or when hours and materials are missing from the invoice data. Then it can be corrected before the invoice goes out.

What AI does is traceable, and you can see where a suggestion came from. Before anything is put into use, we agree together which AI services are used, where the data is processed, and that it is not used to train the models.

How to get started.

  1. 01

    A no-obligation conversation

    A short chat about how you work today, and where there is most to gain in overview and automation. If your current solution is good enough, we will say so. No cost.

  2. 02

    Needs assessment

    For larger needs, we map one process area from start to finish, together with the people who know it. You get a solution outline, a costed plan and a fixed-price offer. The document is yours regardless, even if you choose another supplier.

  3. 03

    We develop the core

    At a fixed price, on the scope that has been described. You follow the progress along the way. The first version is production-ready, with access control and logging in place. Who owns what is set out in the agreement before we start.

  4. 04

    It grows with you

    New modules are added where the bottlenecks show up, not where we guessed in advance. We run the solution on a fixed agreement: monitoring, updates and bug fixes.

If it turns out that an off-the-shelf system covers your needs better, we will tell you. See also system development and PWAs for people in the field.

Frequently asked questions

What is Central X?

Central X is the core system from STUDIO X. It pulls from the systems you already use, gives you one overview of jobs, people and status, and can grow to bring more into one system over time. We own and continue to develop the system itself, and the data is yours.

How do we get started with AI in our organisation?

Start with one concrete task where a lot of time goes into searching, typing or answering the same questions, not with a large AI strategy. Then check whether the information AI needs is available. If it is scattered across several systems, that is the first thing to solve. Central X brings it together, so AI can be used safely on your own data, with a person approving until you see that the suggestions hold up.

Why do Copilot or ChatGPT not deliver more for us?

Usually because the tools cannot see the information that matters for the work. Status, agreements and history live in line-of-business systems, accounting and email that the assistant cannot access, or only partly. General AI tools are useful for text and summaries. The effect on operations comes when AI is connected to joined-up, current data.

Is Central X a fit for municipalities and organisations?

Yes. Municipalities and organisations often have many systems that do not talk to each other, and the same need for overview and safe use of AI. Public procurement rules apply to municipalities, and we adapt to the process you use. We know the privacy and security requirements of the public sector from apps we have developed for Oslo and Øygarden municipalities, among others.

What is a core system?

A core system is the system your business runs on, where jobs, customers, documentation and status are connected in one place. What sets it apart from a standard line-of-business system is that it is adapted to how you work, and that it can pull data from the tools you already use instead of replacing them.

Do we have to replace the systems we have today?

No, and it is usually not wise either. Most start with the systems staying as they are, while we develop a layer on top that pulls data from them. If you later want to bring more into one system, the core can grow in that direction. That is a decision you make along the way, not at the start.

What is MCP, and why is it mentioned?

MCP (Model Context Protocol) is an open standard that lets AI tools and systems fetch data from each other in a controlled way. It means more and more services can be connected without custom work for each one. Where a service offers MCP or a standard API, we can pull data from it. If it offers neither, we will tell you early.

How much of this can run automatically?

That is up to you. A common start is that the system suggests and a person approves, for example when interpreting incoming email and PDFs. Once you see that the suggestions are accurate, more steps can be automated. Everything is traceable, so you can always see who or what made a change, and where a figure came from.

What is AI used for in a core system?

Most commonly to interpret incoming email and documents, answer questions about your own data, draft status updates and customer replies, turn speech into entries in the field, and flag when something slips. At first AI suggests and a person approves. You decide when more can run automatically.

Where does the data end up when AI is used?

We clarify that with you before anything is put into use: which AI services are used, where the data is processed, and that it is not used to train the models. The data in the core is yours, and what AI does is logged. You can see what was suggested, and who approved it.

Who is responsible for operations and security?

STUDIO X develops and runs Central X, so you have one supplier to deal with. We monitor the solution, keep it updated and fix errors under the operations agreement. You are the data controller, and we are the data processor under a separate data processing agreement. The data is stored in the EU/EEA. Who does what is set out in the agreement before we start.

What does it cost, and what does it cost to find out?

The first conversation costs nothing. For larger needs, we carry out a needs assessment at a fixed price, and the amount is deducted from the price if you go ahead. The development itself is priced at a fixed price on a described scope, so you know what it costs before you decide. The price depends on the scope, so we set it after the assessment, not before.

How long before we see something?

The aim is for you to see a working first version early, not a finished system far in the future. We start with the area that gives the most return, often logging from the field or a combined status for management, and extend from there.

What happens if we want to change supplier later?

The data is yours. We own and continue to develop the core system itself, and that is part of the pricing model. How you take your data with you if the collaboration ends is agreed before we start, so it is clear in advance. If you need to own the source code yourselves, a custom solution may be a better fit, and we will tell you so.

Is this a fit for small businesses?

It depends on how much manual work is done today. If you are a small team with simple routines, there are often off-the-shelf tools that cover the need, and we will tell you so. The effect comes when several people move the same information between systems, day after day.

See also all frequently asked questions about price and process.

Talk to one of us.

Tell us briefly how you work today. Together we will see whether there is anything to gain in overview and automation, and we will tell you if your current solution is good enough. That conversation costs nothing.

Daniel Heimstad

Daniel Heimstad

Inbound Lead Manager

Jostein Flatin

Jostein Flatin

CEO / Managing Director