Current-State Friction Map
A documented view of systems, handoffs, duplicate work and approval bottlenecks, grounded in how your team actually operates.
CANADA DIGITAL ADOPTION & REGIONAL PRODUCTIVITY PROGRAMS (QUEBEC / ESSOR / MEIE)
Be On It designs Montreal-native, bilingual-first operating layers and custom internal software. When growing businesses qualify for Canadian and Quebec productivity initiatives, the most difficult hurdle is meeting the stringent technical requirements: formal systems audits, quantifiable productivity benchmarks, and verified execution milestones. We deliver the formal architectural audit that program officers require—and the custom software build that ensures your team actually adopts it.
FROM POLICY TO WORKING CODE
Document the current state, define the target system and identify measurable changes before a build begins.
Design the staff experience, documentation and rollout with English and French operations in mind from the start.
Tie sprint deliverables to testable acceptance criteria and organize records for applicable reporting and disbursement claims.
THE AUDIT PACKAGE
A documented view of systems, handoffs, duplicate work and approval bottlenecks, grounded in how your team actually operates.
A proposed operating architecture: data ownership, integrations, roles, workflows and what should be built around existing software.
A baseline and measurement plan for time, throughput and rework, with assumptions clearly separated from verified results.
Phased build deliverables, acceptance criteria and evidence checkpoints that can be mapped to your program’s claim schedule.
Program rules, eligibility and claim requirements vary and can change. Be On It provides systems architecture and implementation, not grant approval or funding advice; we align deliverables to your confirmed program requirements.
WORKING TEMPLATE
Explore the four-part structure. The full French-first, English-below PDF gives your team space to document verified scope, assumptions and evidence—not a promise of grant approval.
Processes, owners, systems of record, handoffs, baseline evidence
Where work begins and ends
Current tools and data owners
Measured delays and rework
PROGRAM FIT
Approved funding should shape the evidence plan, not the software itself. Program availability, intake windows, eligible applicants and expenses change; confirm current terms directly with the program administrator.
Québec / productivity investment
Depending on the stream and project, a technology transition or productivity investment may include a documented diagnosis, implementation plan and eligible technology costs. Confirm the applicable ESSOR stream and eligible expenses before committing to work.
Québec / program-specific support
MEIE-backed digital transformation support can be delivered through specific calls and partner programs. Diagnostic and implementation support differ by program; there is no single blanket grant for every custom software build.
Canada / innovation R&D
IRAP supports eligible innovation and technology development projects. A routine internal systems rollout is not automatically an R&D project; its technical novelty and program fit must be assessed separately.
POTENTIAL FIT
Custom workflows, integration with existing systems, measurable productivity changes and bilingual interfaces can strengthen a documented project scope. Whether any cost qualifies depends on the specific stream, applicant and approved budget.
NOT A FUNDING ASSUMPTION
An off-the-shelf licence, routine subscription or standard rollout alone should not be treated as eligible custom development. IRAP in particular requires an eligible innovation project, not simply an internal software purchase.
Be On It provides technical scoping and implementation, not grant approval or eligibility advice. No program endorsement or funding outcome is implied.
Human-layer adoption architecture
Pilot one workflow, prove that people can use it, then expand. Training objectives, operating ownership and acceptance evidence are part of the Blueprint—not an afterthought.
01 / Before pilot
Role map, baseline sample, French and English task guides
Owner: Process owner + team lead
Go / no-go: Owners agree on the workflow and baseline evidence.
02 / One team / one workflow
Supervised practice, exception log and user feedback
Owner: Pilot users + Be On It
Go / no-go: Users complete the core task and an exception without assistance.
03 / After pilot sign-off
Role-based sessions, access checks and handover records
Owner: Team leads + internal champions
Go / no-go: Each role has a trained backup and signed acceptance checklist.
04 / After rollout
Office hours, measured follow-up and updated quick references
Owner: Process owner + support
Go / no-go: Compare matched samples; resolve open exceptions before closing rollout.
Role-specific French and English task sheets cover the action, expected result, exception path and named internal contact. Screenshots and escalation contacts are finalized against your deployed system.
Proposed planning schedule: 8 session hours across distinct audiences, not 8 hours per employee. Adjust after the training needs analysis. Participant wages, trainer fees and software onboarding are budgeted separately.
| Activity / audience | Hours | Evidence |
|---|---|---|
| Training needs analysisTeam leads | 1 | Role gaps, objectives and initial skill assessment |
| Core workflow practiceOperational users | 2 | Attendance, practice scenario and completion rubric |
| Approvals and exceptionsApprovers + backups | 1.5 | Escalation scenario and independent competency check |
| Reporting and data qualityManagers + finance | 1.5 | Reconciliation exercise and reporting checklist |
| Internal champion handoverInternal champions | 1 | Teach-back assessment and support ownership |
| Post-rollout skills reviewRole representatives | 1 | Follow-up assessment and outstanding learning needs |
Productivité-Compétences is call-specific: the published management-training call uses collective promoters and workers from multiple companies. A single-company software onboarding schedule is not automatically eligible. Confirm the appropriate call, promoter, curriculum, qualified trainer and eligible expenses before making any funding assumption.
Blueprint / finance handover
A French-first service-offer structure aligned to the published Annex A checklist. The Blueprint defines the architecture; a separately itemized implementation offer maps the work to a qualifying digital plan.
The Volet 1C guide requires a digital plan resulting specifically from Volet 1B within the preceding 24 months. Confirm that prerequisite with Investissement Québec. Costs and contractual commitments made before filing are excluded; filing itself does not guarantee funding. The guide also specifies applicant size and revenue criteria, and francisation evidence where applicable.
Consultant identity, project lead, contact information, relevant expertise and verified similar mandates; beneficiary legal name, site address and organizational context.
Title, need, objectives, retained systems, activities, exclusions, tangible deliverables, start/end dates and total quote amount.
Amount per stage; hours and hourly rate or fixed fee. Separate taxes, licences, internal costs, training and support from fees submitted for eligibility review.
Reference the qualifying digital plan, approved scope and exclusions
Acceptance: Client finance confirms filing requirements
Preparation / separately scoped · Dates and fees confirmed in the client offer.
Configured workflow, interfaces and access matrix
Acceptance: Documented integration and permission tests
Implementation fees / to be assessed · Dates and fees confirmed in the client offer.
Pilot deployment, test record and corrections
Acceptance: Process owner signs functional acceptance
Implementation fees / to be assessed · Dates and fees confirmed in the client offer.
Production release, operating documentation and handover
Acceptance: Release and handover signed; evidence indexed
Implementation fees / to be assessed · Dates and fees confirmed in the client offer.
Finance handover: French service offer, qualifying plan reference, project description and financing schedule, indexed deliverables, invoices, payment evidence and acceptance records. Financial statements, required consent forms and francisation documents remain the applicant’s responsibility. Claim timing follows the actual funding letter; no duplicated expense claims across programs.
Planning template, not an approved application or compliance certification. Final French offer, consultant qualifications, applicant eligibility and current rules must be validated for the specific mandate.
START WITH YOUR OPERATION
Tell us where systems and teams lose time. We’ll use that starting point to discuss scope, evidence and a practical build sequence.