The Seven Steps of the Transition
- 01
We assess your current structure together
We take up your business model, the tools you use and your priorities.
- 02
Together we set your priority
We choose which flow to build first: sales, inventory, finance, manufacturing, field or team.
- 03
You see the structure that fits you
We walk through marqey with flows close to your business; watch how the screens sit on your work.
- 04
We settle the scope and the transition
We select the first products, roles, data and integrations, and draw up the transition plan.
- 05
We install, adapt and train
We prepare screens, fields and reports to match the way you work, and get your team used to daily use.
- 06
We go live and stay at your side
We are on hand on transition day; we handle your questions and correction requests within the support routine.
- 07
We extend as needs arise
Once the first structure settles, we add new products, modules and service connections to the same order.
Our Working Principles
The quote stays lean until the scope is clear
First we establish what you need.
We plan the transition so your business doesn't stop
Your current setup keeps running until the new structure goes live; downtime risk gets addressed in the transition plan.
Your business language stays intact
We build the screens with your terms, and your team recognises its own work in the new system.
We prefer a phased transition
Rather than changing everything at once, we start at the most critical point.
Team adoption gets its own plan
We plan daily user habits alongside management reports.
We leave room for growth
We do not close off the structure against future processes.
What We Expect from You
One person who owns the process
A single point of contact who speeds up decisions throughout the installation.
A real piece of work to examine together
We work through a sample order or project to make the process concrete.
Attendance at the sessions
Installation proceeds in one-to-two-hour sessions per week, alternating between online and on-site work; downtime risk gets addressed in the transition plan.
Things you do not need at the start
You do not need to open accounts for the whole team, migrate every historical detail on day one, or drop your current programs at once.
Frequently Asked Questions
How is the price set?
By your scope: once your needs are clear, you receive a quote based on the modules to install and the customisation you need. The budget is phased and the total of the starting scope is known from the start. Work outside that scope gets priced separately. You begin with a small scope and add modules as needs arise. The Pricing page has the detail.
Will our arrangement with our accountant break?
No. You keep working with your accountant. marqey manages your daily operation and prepares the records that go to accounting, orderly and complete.
Are e-Fatura and e-Arşiv, Türkiye's electronic invoicing documents, supported?
Yes. If the workflow depends on these documents, the first scope can include the service, document types and data direction. Users issue them from the related sales or dispatch record.
Will our team learn to use it?
Yes. Training uses the team’s real order, warehouse, manufacturing or field scenarios. Each user practises opening, handing off and closing records with their own permissions before go-live.
Will our existing data migrate?
Bulk transfer of master data such as customers, products and stock is part of the installation scope. We review the content and quality of the data to migrate together.
When is the migration schedule confirmed?
The schedule is written into the proposal and migration plan after the data condition, user roles, required connections, and first scope have been reviewed. Later phases are planned against their own scope.
How does support work after go-live?
The monthly service lists hosting, backups, system monitoring, updates and the agreed support channels. The contract also explains how new development or scope-expansion requests are handled.
Is our data safe?
The system runs on your own server or in a cloud environment that belongs to you. The permission structure and audit trails stay with you.
Do we have to decide in the first meeting?
No. The first meeting identifies the current tools, one example workflow and the result management needs to see. Scope and timing follow after the required review.
Is marqey right for every business?
No. Very small teams whose current program covers their basic record-keeping do not need marqey. marqey earns its place in businesses that want to connect their processes.