Services · Implementation
We map your entities, chart of accounts and process boundaries, configure the instance, and run parallel until the numbers agree in both systems. Alpine handles the configuration; we handle the decisions that need judgement.
The work
An AlpineERP implementation fails in one of two ways: the configuration was never really finished, or the business was never really ready. The software is rarely the problem. AlpineERP ships with every module a mid-sized business needs, documented end to end. What it does not ship with is your chart of accounts, your approval chains, your warehouse topology and your idea of a completed order.
Our implementation service puts those into the platform. We build the fields, workflows and permission roles around the processes agreed in discovery, and our architects make the judgement calls that decide whether a rollout works: which entities to consolidate, which legacy processes to retire rather than replicate, and where a two-week parallel run is worth its cost.
What you get
Named up front so the engagement has a definition of done.
Every in-scope process described on one page: trigger, steps, decision points, owners. You approve this before anything is configured, so the argument about how returns work happens in week two, not week eight.
Chart of accounts, entity structure, warehouses, item groups, roles, naming series, print formats and the workflows themselves: generated by Alpine, reviewed object by object by an architect, and staged in a sandbox you can click through.
Both systems live at once, with daily variance reports until the deltas are zero for three consecutive days. The cutover is a formality after that, not a cliff.
Role-based training and administrator sessions, plus documentation written against your processes rather than generic ones. The measure of success is that the next workflow is built by your people, not by us.
Pricing
No day rates and no sticker price. The estimate is derived from your situation. Each answer moves it, and anything genuinely unusual is scoped rather than guessed.
Estimated implementation cost
$2,000
fixed, one-time
An estimate, not a quote. We confirm the fixed price against a written scope before any work starts.
Platform plans are priced separately on the pricing page. This estimate covers the implementation itself.
Questions
Because Alpine generates the configuration work (fields, workflows, roles), which is where most implementation hours traditionally go. What remains is judgement and testing, and those are predictable enough to scope. If discovery reveals something genuinely outside the model, we re-scope with you before proceeding, not after.
It is a transparent model, not a black box: a base implementation, plus a fixed add-on per choice you make. More users, multiple entities and deeper modules each add a named amount, so you can see exactly what moved the number. Anything beyond the model (a very large deployment, unusual legacy sources) resolves to a paid discovery phase and a fixed quote against its findings.
Yes, and we will say so when it is the right answer. The ledger is the one non-negotiable. Everything else can land in waves. A common pattern is finance and stock first, manufacturing six months later.
A decision-owner per process area, access to the current system's data, and roughly four hours a week from your project lead during discovery and the parallel run. Implementations stall on absent decision-makers more than on anything technical.
The go-live fortnight is included, then most customers move to managed hosting with a support plan: Essential or Premium. The implementation team hands over to a named success architect who already knows your setup.
