Custom admin interfaces
A back-office is the private screen from which you steer what happens behind your website or your tool: editing, tracking, authorising. FastSolve builds it so you stop depending on somebody else for every change.
You can see the result before discussing it: the link below is available online, with no sign-up required.
Waiting three days to change a price
Four situations turn up as soon as a business grows past a handful of files.
- Changing a price on your website means writing to somebody, waiting for them to be free, then checking they understood what you meant.
- Enquiries arrive by email and their progress is tracked in a thread. Nobody knows where Tuesday's one stands.
- One person holds the access. When they are away, nothing moves.
- The whole team sees everything, including what it should not, because splitting access was never planned for.
The real cost is not the technical step, which takes two minutes. It is the delay, the dependency, and the decisions put off because changing them looks complicated.
Four functions of a back-office
Most of the requests we handle combine all or part of these four functions.
1. Publishing without a middleman
Text, prices, photographs, records: whatever changes often should be editable by you, from a clear screen, without touching the code and without risking the layout.
Typical case. A restaurant owner had a supplier update the menu each season. He now updates it himself in the morning, and the site is current by midday.
2. Tracking what is moving
Received, in progress, waiting on information, done. A visible status replaces memory and email threads, and surfaces first whatever has been sitting too long.
Typical case. A workshop tracked repairs in a notebook. Every job now carries a status and a date, and clients who ring get an answer in ten seconds.
3. Giving each person what concerns them
A well-divided back-office shows each person what they need and nothing more. That protects your data, but above all it prevents mistakes made in good faith.
Typical case. A small firm gave everyone the same access. Prices are now restricted to management, data entry stays open to the team, and nobody changes a discount by accident.
4. Keeping the trail
Knowing who changed what and when settles most arguments. A change log turns a disagreement into a question of fact, and lets you go back.
Typical case. A merchant wanted to know who had altered a selling price. The log answered in a minute, and an approval rule was added the next day.
What a back-office will not do
It makes you self-sufficient on day-to-day matters. It does not run the business for you.
- It does not replace a full business suite. Bringing accounting, payroll and stock together in a single product is a different service, one FastSolve also handles: a larger project, scoped and quoted separately.
- It does not invent your organisation. If the statuses are unclear in people's heads, putting them on screen will not clarify them.
- It does not prevent every mistake. It makes them visible and reversible, which is more realistic than claiming to abolish them.
- It does not secure what depends on you. Passwords shared between five people undo the best-designed access split.
The gain is in independence and in speed, not in the management decisions, which stay yours.
Frequently asked questions
How much does an admin interface cost?
The amount depends on how many kinds of item have to be managed, how many distinct roles there are, and whether a history and an approval step are needed. A content editing screen and a four-role back-office with a change log are in no way comparable. The price is set after scoping. As a guide, excluding VAT, most admin interfaces fall between 2,500 and 5,000 euros. A back office with several roles and a change log can reach 9,000 euros.
Can it be plugged into an existing site?
Usually yes, provided the data is reachable. That is exactly what gets checked during scoping, before any pricing, because the answer changes the effort considerably.
What happens if someone makes a mistake?
Changes are recorded with their author and their date, and important items can be restored. On consequential actions, approval by a second person can be required, if you want it.
How many people can use it?
There is no per-user licence: the number of accounts is yours to decide. What matters during scoping is the number of different roles, because that is what drives the work.
Is training needed?
The aim is for anyone to pick it up in a few minutes. A back-office people are afraid to use sends everyone back to the old habits, and the project changed nothing.
Tell us what you cannot change yourself
See how a project runs, from scoping to delivery
See all FastSolve services