Cost and scope

When the workflow, system access or feasibility is unclear, an assessment can define a practical next step before you commit to implementation. We review the agreed work, existing capabilities and constraints, then set out the options and recommended scope.

• Focused workflow review — from CAD 2,500: One workflow involving up to two systems. Review the handoffs, existing features and access requirements, then identify a suitable next step.
• Systems & workflow assessment — from CAD 5,000: One substantial workflow, up to three systems and four stakeholders, with one bounded feasibility check. The report and implementation plan cover the workflow, dependencies, findings and recommended scope. We agree on the check, required access and depth of review before starting.
• Larger assessments: Custom-scoped when the number of systems, teams or questions calls for a wider review.

These are starting prices for standalone assessments, excluding applicable tax. We agree on the scope and fixed fee before work starts. Implementation is quoted separately; an assessment fee is not an implementation budget.

You receive a portable written report and next-step plan covering the agreed review. You can use them with Snoogz, your own team or another provider; continuing with Snoogz for implementation is optional.

A paid assessment is not required for every project. A straightforward website or well-defined fix can go directly to a scoped quote.

The number of screens is only part of the work. A small screen may need several roles, a difficult calculation or a connection to a system with limited access. Describe the behavior behind it.

• People and permissions: who can view, change, approve and export each record.
• Rules and exceptions: calculations, status changes and cases that need someone to decide.
• Connections: available interfaces, matching IDs, update direction and what happens when a service fails.
• Existing data: cleanup, field mapping, trial imports and checks before the switch.
• Review and launch: realistic test examples, feedback, deployment and instructions for the people using the result.

Unresolved questions create work too. If a provider's access or an old workbook's calculation is uncertain, an assessment may be useful before implementation is quoted. The proposal should identify assumptions, dependencies and what would require a change in scope.

Consider the illustrative customer portal. Its first release could let a customer submit one type of request, attach the required file and see an outcome. Staff would review the request, ask for missing information and record the handoff.

That scope still needs permissions, error handling and a review process. It does not automatically include payments, scheduling, live chat or a migration of every past request. Each of those can be assessed separately instead of staying hidden inside the word “portal.”

For this example, review cases would include a complete request, a missing file, an unsupported file type and an attempt to open another customer’s record. Those checks belong in the scope and testing of the working portal.

Describe one task from start to finish. A brief becomes easier to discuss when it includes:

• What starts the work and what a completed result looks like.
• Who performs each part and who approves the result.
• The tools holding the information today.
• How often it happens and which exceptions need attention.
• Which existing records need to move.
• A budget expectation, a desired start and any date with a real dependency.

You can begin with Snoogz's five-question enquiry and add these details in the email it prepares. The questions collect the type of engagement, starting point, preferred timing, initial budget and priorities. They do not collect the systems, fields or business rules needed for a full scope. Remove private customer information from examples shared at this stage.

When reviewing a proposal, check the result it includes, the assumptions behind it and the work it excludes. Look for the review points, access requirements, migration checks and handover, as well as the price. Two proposals can use the same project name while describing different amounts of work.

Snoogz normally owns a defined project through delivery and handover, working directly with you through Jacky Pham. If you already have an engineering team, embedded support for an agreed workstream is another option. Responsibilities, availability and ongoing support are scoped with that team.

For internal tools and reporting, start with custom software. For repeated handoffs and connections, see workflow automation. For public pages and enquiries, see websites.