Driving Implementation Success
The struggle
An implementation is a purely technical effort intended to get a new or improved tool online. A transformation is an effort that combines the implementation of a tool with an update and a realignment of business processes.
Organizations struggle with whether to perform a transformation or simply execute a technology implementation. Transformations typically carry a much higher price tag and require a much longer runway to completion.
Ultimately, most organizations either bite off more than they can chew or far too little. The latter results in an implementation that breaks processes and destroys business value.
Perception of the end result suffers, and the sponsors suffer for years. We understand the stress.
We'll provide guidance even if the budgets are razor-thin. That's what partners do.
What is Transformation Lite?
Most consulting firms lack the resource depth to execute an implementation with an MVP-focused update to business processes.
Fortunately, Proforma leadership understands that tools simply cannot be implemented without considering processes.
The 'Proforma way' consists of 3 types of approaches:
1. Implementation only (11-14 weeks) - A technical implementation that focuses on technical deliverables. As the project progresses, Proforma leadership will informally identify and discuss likely process, reporting, and change management gaps that the Finance/Accounting teams can address internally.
2. Transformation Lite (14-17 weeks) - A technical implementation with a MVP-focused process assessment producing high-level best practice process flows and change management takeaways to reduce the inevitable impact new tools will have on existing business processes.
This method is most useful for Fire-Aim-Fire approaches, where a rapid application deployment occurs, followed by enhancements and updates to business processes after the initial go-live.
3. Full Transformation (~24-42 weeks) - Best suited for larger initiatives covering multiple workstreams and business processes, or organizations that are more comfortable with waterfall-based delivery methodologies.
The initiative will cover process, technology, and change management.
What does a full transformation consist of?
Phase / SOW 1
Current State Assessment (3-5 weeks) - Process and pain point focused workshops.
Future (and interim) State Process Design (3-5 weeks) - Review of best practices and recommendations after current state has been absorbed.
Formalization (2-4 weeks) - Heads-down time focused on documenting process flows and developing a change management approach that highlights the significant gaps to be caused by implementing the new tool.
Phase / SOW 2
Technical Design & Prototyping (2-4 weeks) - Translate the process and requirements gathered in the first phase into a technical application. The technical design produces application prototypes to ensure the business understands the look, feel, and what the end-result will materially look like.
Phase / SOW 3
Build / Test & Train (8-12 weeks) - Technical development of objects such as hierarchies, calculations, integrations, input forms, reports, and security.
Data validation runs in parallel, driven by the internal Finance/Accounting teams.
Testing and end-user training cycles occur during the last 4 weeks of the project.
We thrive based on our customer satisfaction and referrals.
Outcome-based billing is preferred
Although we offer engagements that are based on total hours billed at an hourly rate, we prefer fixed-fee pricing.
Our team's superior talent enables us to deliver higher quality products and pass some of those cost savings to you. We have complete trust in our team and their abilities.
Some firms simply staff projects with any warm body - that's the antithesis of how we operate. If we don't have the right resource mix, we simply won't take on the work.
We do not intend to participate in the 80% of the projects that fail.
Quality of delivery over revenue.