CloudScaff questions and answers
Pricing projects and evaluating CloudScaff
Answers to 12 questions about pricing projects and evaluating cloudscaff.
12 questions
Questions in this topic
12 answersHow is CloudScaff priced?
CloudScaff pricing is based on active project capacity, with unlimited users. Choose the capacity that fits the number of projects you need to manage at the same time.
The pricing page lists the current plans and billing options. It is the best reference for current amounts, rather than a price quoted in an older demonstration or recording.
Is there a free plan?
Yes. The current pricing page lists a free plan for up to three active projects. This provides a starting point for evaluating the system with a small number of jobs.
Use the evaluation to test complete workflows, including returns and exceptions, rather than only creating sample inventory. Confirm the current plan terms on the pricing page when you sign up.
What is an active project?
An active project is a site or job record that remains open for ongoing work in the system. Project capacity is about the work you keep active, rather than the lifetime number of jobs your business has completed.
Agree how your real operation will be represented. One facility may contain multiple scaffold records, while separately managed work areas may be set up as separate projects with implications for capacity.
Is a scaffold the same thing as a billable project?
Not necessarily. A project can contain several scaffold records, so counting individual structures does not automatically tell you which project plan you need.
Review your intended site structure during the demonstration. If you divide a facility into separate project records for floors, areas, or teams, use that actual configuration when estimating the capacity required.
What happens when we reach our project limit?
You can close a genuinely completed project to free capacity or move to a plan with more active projects. The current pricing page describes these options.
Before closing a job, resolve its outstanding operational work and inventory. Do not close an ongoing project solely to create room if your team still needs to transact against it.
Do we lose the history when we close a project?
Closing a project is intended to preserve its historical records for reference while removing it from active work. Your team can review past project information without keeping every completed job active.
This is separate from account cancellation or a contractual data-retention requirement. If either matters to your business, confirm the relevant terms and export arrangements before making a decision.
Do plans charge separately for each user?
CloudScaff's published model includes unlimited users rather than a per-user charge. Plan selection is based on the active project capacity required.
Check the current commercial scope for any separately scoped implementation or integration work. Unlimited users describes user access; it should not be read as an unlimited commitment to every possible custom development request.
Are monthly and longer billing options available?
The pricing page lists monthly, yearly, and three-year billing options. Review the current offer and terms when choosing a billing period.
For questions about upgrades, downgrades, renewal, cancellation, or a particular payment method, confirm the arrangement with CloudScaff before purchase. Those details should follow your actual subscription terms.
Can we see a demonstration based on our workflow?
Yes. A useful demonstration starts with how your business requests equipment, dispatches it, manages it on site, and accounts for its return. Include scaffold documentation if that is part of your requirement.
Bring a sample stock list, material request, delivery note, return sheet, or handover form. Real examples make it easier to check fit and identify setup requirements than a purely generic walkthrough.
What should we test before deciding?
Test a complete working cycle with representative equipment and users: a request, a partial delivery, receipt, a site transfer, and a return with a discrepancy or damaged item. Then check the resulting balances and documents.
If scaffold management matters, also create a scaffold, complete a handover and inspection, record a change, and review the dismantle history. Test customer access and exports using the actual roles your team will use.
How should we evaluate CloudScaff against another system?
Compare the workflows that cause the most work or risk in your operation. Look at how each system handles incomplete deliveries, site transfers, returns, supplier stock, stock adjustments, and the evidence behind each balance.
Also assess field usability, data migration, permissions, reporting, and the systems that must remain connected. Use the same real examples in each demonstration so the comparison is based on your operating requirements.
How do we get started?
Start with the CloudScaff pricing page to review the available plans, or use the CloudScaff website to arrange a demonstration.
Tell the team what you manage, how many projects and yards you operate, and where your current process becomes difficult. From there, you can agree the data, configuration, and training needed for a useful first rollout.
No matching questions. Try another search or topic.