Internal system for SMEs

How it works

From sign-up to live in about half an hour

There is no rollout project, no consultant day rate and nobody new to hire. This page walks through what happens in the first half hour, what happens in the first week, what happens as the company grows, and what happens when you need something that is not in there yet.

Start the free trial Open the demo

Before you decide

You can look at it, and you can try it, before deciding

This part comes first because it shows what you can see and test before you commit to anything. The demo and the trial are two different things, and it is better to know the difference up front.

You open the demo

You do not have to give us anything, not even an email address, a company name or a card. The demo is a shared environment anyone can open, holding the full data of an invented company. Some features are switched off in it, and every night it resets to its starting state, so nothing you do there is kept. It is for looking, not for working.

You start your own trial

This one is your system, at your own address, with full functionality and your own data. That is what can actually be evaluated, because a shared showcase environment cannot tell you whether it fits your work. It starts free, without a card, and nobody calls you.

If it is not for you, you cancel

It ends the way a streaming subscription ends, with no minimum term, no exit fee and no explanation. That applies to the trial and to the subscription. With the demo there is nothing to cancel, because nothing was started.

Take a look inside

The demo opens with no sign-up and no card, and it resets to its base state every night. If you would like to see it working on your own projects, that is what the trial is for.

No sign-up
No bank card
Full functionality

Open the demo Start the free trial

Getting started

The first half hour of your trial

From here on this is about the trial, not the demo, because nothing is installed when you only look at the demo. There is nothing to download and nobody to hire. After you sign up, the system installs itself at your own address, and by the time you first log in it is working. That takes about thirty minutes, and only a few of those minutes need your attention.

~30 min automatic setup on the trial, from sign-up to first login

0 setup fee, no mandatory consultancy line

Built in manual and walkthrough inside the app

What happens during that half hour

None of it needs you to sit in front of the screen. The steps go at your pace, and you can stop after any of them without leaving the system half configured.

You sign up

All you need is a work email address and a password. There is no credit card, and nobody calls to book a discovery session first. If you are still only looking around, you can skip this step entirely, because the demo is there for that and needs no sign-up.

Setup runs

From here there is nothing for you to do. The system comes up at your own address, in a separate environment with its own database. The practical benefit is that when another customer has a problem, you do not feel it, either as downtime or as a slowdown.

You log in and the walkthrough starts

On first login the system shows you where things are. The manual is inside the app too, not a PDF somewhere in your inbox, so you can find the answer at the point where you got stuck. That is why there is no training day on the invoice, because there is nothing for it to do.

You bring your colleagues in

You can send invitations by email, one at a time or all at once. Everyone sees what their role allows, so you do not have to open the rollout by deciding who may look at payroll. The default is usable, and you can change it later.

Decisions

What you have to decide now, and what can wait

Most rollouts do not fail because of the software. They fail because on day one you are asked for thirty decisions about things you have not yet seen working. Here there are three decisions, and the rest can wait.

What genuinely cannot wait

Who is in, what each of them may see, and where the data starts, from your existing spreadsheets or from nothing. That is the list. Once those three are settled the system is usable, and everything else you shape as you go.

What can wait

Modelling your processes in detail can wait. This is where rollouts stall for months, because everyone tries to design in advance how the company ought to work. Two weeks of real use tells you more about that than two weeks of meetings, and afterwards you will know what to change.

The person who hates new systems

Most teams have one or two people who have struggled with every new tool so far. What matters to them is that day one is not an empty screen, and that whatever they get wrong can be undone. Both are covered below, and neither is there by accident.

The questions that matter

Three fears with a simple answer

Nobody says these in a sales conversation, and all three of them are what the decision actually turns on.

We have no IT person

You do not need one. Nothing is installed on anyone's machine, there is no server to maintain, and there is no update someone has to run at the weekend. What has to be set up is users and roles, and that is done by whoever in the company already knows who does what. If you do want help, our specialists are glad to give it.

The team will not use it anyway

This is the most common fear, and the most reasonable one. Two things work against it, and both are built in. Imports mean that day one does not start with an empty screen, and the trash means that a wrong click can be undone. The first few weeks decide the rest. If the team does not use it, you simply cancel.

We already pay for five subscriptions

If you have five or ten separate subscriptions running today, that is not a system, it is five or ten places where the same information sits slightly differently. You do not have to replace them all at once. Most companies start with one area and cancel something once they can see they genuinely do not miss it.

Platform

Things that make it easier to use

These four are the points a system usually fails on. Each one answers a specific failure, and every one of those failures only shows up in use, by which time it is hard to turn back.

Dashboard builder

If everyone gets the same landing screen, full of numbers that are not their concern, nobody looks at it after two weeks. So each person builds their own dashboard from the modules they actually use. Sales sees enquiries first, the project lead sees deadlines, the owner sees what is stuck.

Model & event log

When someone changes a date and nobody knows who did it or when, half an hour can go on sorting it out. The log records what changed, who changed it and when, in every module. It is not there to police anyone. It is there so the question gets settled instead of argued. Its entries cannot be edited or deleted afterwards, because a log that can be rewritten proves nothing. The same principle runs through the whole system. A sent quotation is locked, an issued invoice cannot be deleted, only cancelled, a published form never changes afterwards, and neither does a closed payroll month.

Imports

If day one of a new system is an empty screen, everyone goes back to the spreadsheet, and three months later you are keeping the same data in two places. That is why your existing spreadsheets can be imported at the start, from customers through leads and the catalogue to employees. You see a preview first, and a partly broken file is never loaded. Exports work the same way, all under one menu item, with column headings in your own language.

Trash

One accidental deletion that cannot be undone is enough for nobody in the team to dare touch anything again. Deleted records can be restored, so a wrong click is not a lost afternoon. It is the least impressive feature on this list, and the one used most often.

A dashboard in IntrApp, with the number of boards, customers, leads and users at the top, then tasks and tickets by priority, leads by status, your tickets and overdue tasks.

When the company changes

What happens when the company changes

You find out what a system is really like when the team grows, when somebody leaves, or when a requirement turns up that nobody planned for. Those are the three cases.

Somebody joins

You pay per person, so one more colleague does not mean buying the next package up, and you do not have to wait for a contract anniversary either. You invite them, they get a role, and on first login they get the same walkthrough you did. The pricing detail is on the pricing page.

Somebody leaves

This is the day you find out how much of the company lived in one person's head and inbox. What they did in IntrApp stays with the projects and the customers, not with them. You remove their access, the work is still there, and the log shows where they had got to.

You need something that is not in there

This is not a dead end, and it is not “we will add it to the list” either. You describe what is missing, and we tell you up front which way it falls. Some requests we build for free for everyone, and others become paid custom work that keeps receiving the shared updates. Where the line runs is set out on the custom development page.

Operations

What you do not have to look after

There is nothing for you to maintain and no system administrator to keep on staff.

Every customer runs in a separate environment with its own database, at its own address, and we watch it continuously. We usually know about a fault before you do, and it is typically fixed before you would have noticed. If it is not, you can write to us inside the app, and from then on the problem is ours. Every change goes through automated tests before it goes live.