1C implementation that ends with a closed month, not with an invoice
Only about one automation project in ten reaches its goals. Not because of bad programmers — because companies install a program instead of building order, and put people in front of a fait accompli. Our technology is built around that observation.
Five working principles
We collect the truth about the business
Processes are documented the way they actually work — including workarounds and spreadsheets — not the way job descriptions say they should.
Your experts defend the processes
A process map is presented to the team not by our analyst, but by your employee who works in that process. Then it is their process — and there is no sabotage at launch.
Show first, program later
You see a demo base of the future solution before signing, and modelled processes live in 1C before a single line of custom code is written. Expensive changes of direction happen on diagrams, not in code.
People learn before go-live
Every user passes training on their own case and gets a certificate. The system starts with people who already know how to work in it.
The effect is measured
Key metrics are measured before the project and after launch. The result is visible in numbers, not in feelings.
Staged contracts
The contract is signed stage by stage: you always know the exact price and deadline of the next step before it starts — never a black-box total for "everything".
Nine steps
Introduction
Brief, a presentation of the approach, a demo base of a possible solution — before any contract.
Diagnostics
Interviews, system and server audit, AI analysis of customizations, a health index of your 1C, metrics baseline — and an exact price for the next stage.
Processes As Is
BPMN maps of how the business works today, a loss journal, a signed project charter.
Modelling To Be
Future processes with fewer losses, target IT architecture, and a live demo base — before the technical specification.
Specs & development
Technical specs only for real functional gaps; development through extensions; testing and expert acceptance.
Training
Video and written instructions, group training, personal test cases, certificates — all before go-live.
Base setup
Master data, roles and permissions, exchanges, migration of opening balances on launch date.
Launch
A reinforced team on both sides, a stress test, daily interim closing. The launch counts only when the first real month is closed in the new system.
Handover & analysis
Seamless transition to support, metrics after vs before, NPS, and a plan for the next automation wave.
Frequently asked questions
How long does an implementation take?
From a few months for a focused scope to a year and more for a full ERP. After diagnostics you get a staged plan with dates — and you can stop after any stage with usable results in hand.
Do we have to stop the business during the switch?
No. The new system is prepared and tested on a copy; the switch happens on a planned date with opening balances, and the launch team supports users daily.
What if we only need a small part automated?
Then we do a small project — warehouse, sales, or finance first. The staged model exists exactly for that.
Talk to us
Tell us what hurts — we will honestly say whether we can help, and show how everything works on a live example.
© iTeal · 1C:Enterprise support and implementation in Europe · Belgrade, Serbia