Frequently asked questions.

We start with a short conversation about how the operation works today, where information is held and what is slowing the team down. If SmartCo looks like a sensible fit, we then agree the next step and show you the most relevant parts of the platform.

A proven SmartCo sector build can be provisioned quickly. Full go-live depends on your data, configuration, integrations, testing and any bespoke requirements. We confirm the implementation timetable during discovery rather than publish one number that may not fit every client.

We prefer to understand what you need first so the demonstration is relevant to your operation. The website includes sample product views, and a tailored demo can be arranged when there is a genuine project to discuss.

Yes. Data migration from an agreed existing source is part of implementation. We map and check the data before go-live rather than expecting staff to start again.

Yes. SmartCo is designed as an ongoing managed platform. We support the system, maintain the core platform and can extend it as the operation changes.

SmartCo already has the foundation for users, records, permissions, reporting, security and integrations. We configure and extend that platform around your operation, so development effort goes into the parts that are genuinely specific to your business.

Terminology, records, forms, permissions, dashboards, workflow, approvals, reporting, portals, specialist modules and integrations can all be shaped around the project where appropriate.

Yes, where the project needs a specialist data platform, automation or custom processing outside the core SmartCo CRM platform. SmartCo can coordinate Django and Python development through trusted specialist development partners, with the work scoped clearly as part of the wider solution.

They can be useful where the main requirement is centralising information from several systems, processing or validating large amounts of data, building specialist automation, creating a standalone operational application or providing an integration layer between existing platforms.

Yes. A specialist application can operate alongside SmartCo and exchange the agreed information through APIs or other controlled data interfaces. The aim is to use the right tool for each part of the operation rather than force every requirement into one technology.

The platform can be extended. The ongoing relationship is designed to stop the system becoming another piece of software the business eventually has to work around.

For the standard Essential and Training plans there is no separate implementation fee. Operations and ERP is scoped around the deployment because the range of work can be much wider.

Ten users are included with Essential and Training and LMS. Additional users are £20 per month each. Operations user numbers are agreed as part of the scope.

Supported SmartCo connectors do not carry a separate per-connector licence fee. Third-party providers may charge their own fees, and bespoke connector development is scoped where needed.

Standard configuration is part of the platform. New modules or substantial bespoke functionality are scoped and agreed before work begins.

The range can be very wide. A single-site operation and a multi-site asset-heavy deployment need different levels of configuration, migration and integration. We scope the work properly and agree the figure before you commit.

There is a staff portal that installs to the home screen on iOS and Android and is being extended. Offline support, so notes and check-ins queue when there is no signal in a property, is in active development. We will be straight with you about exactly what is ready at the time you ask.

Yes. Migrating client records, staff records and compliance dates from spreadsheets or an existing system is included rather than charged as an extra.

Yes. UK hosting is available for SmartCo deployments, and we manage updates, backups and support as part of the managed service.

Yes. White-label deployment can put the system on your domain with your branding throughout.

We can change the software. If the way you work changes, the system can be extended rather than forcing the team into another workaround.

Yes. Each has their own portal with its own permissions. Teachers see their classes and learners; learners see only their own record, materials and fees.

Yes. Funding status is held against the learner, and reporting can be filtered by it, so mixed cohorts are handled without a parallel spreadsheet.

No. Migration is planned around your intakes so it does not land mid-cohort. Data migration from your current system is included.

Yes. White-label deployment can put the platform on your domain with your branding, including the learner-facing experience.

We can build it. Bespoke development is scoped and priced before work begins, and the agreed functionality becomes part of your system rather than another external workaround.

Yes. Quick capture is designed for practical field use rather than simply shrinking a desktop form onto a phone.

Yes. The commission matrix can define the split and apply the agreed rules as jobs progress, including where several people worked on the same deal.

Yes, and for larger operations that can extend into stock and purchasing through the Operations platform.

Rounds and territories can be allocated to field staff, with duplicate checks helping to reduce two people working the same location.

If the provider exposes a suitable API or supported data exchange method, it may be connectable. Any bespoke connector work is scoped before it starts.

The range is too wide for one headline figure to be meaningful. A single-site operation and a multi-depot organisation are different deployments, so we scope the work and agree the figure before you commit.

Yes. Multi-site and multi-company structures can be supported where they form part of the agreed deployment.

Yes, where it is useful. A portal can give clients controlled access to project progress, documents or other agreed information without staff manually sending every update.

Yes, where the required API or supported connection is available. Xero, QuickBooks and Sage are examples of systems that can be considered during integration scoping.

The timetable is agreed at scoping. Asset-heavy deployments usually need more migration, configuration and testing than a standard CRM, so the plan is based on the real project rather than a generic promise.

There is no separate per-connector licence charge for supported SmartCo integrations. Any third-party service still charges its own fees, and a genuinely bespoke connector may need development work that is scoped before it starts.

If the system exposes a usable API, webhook or supported data exchange method, it may still be connectable. We review the technical options before promising a specific integration.

Supported integrations are maintained as part of the SmartCo service. If a third-party provider makes a major change that requires new bespoke development, we explain that before any chargeable work starts.

Yes, where appropriate. Access is controlled by authentication and permissions, and we agree the data and actions that should be available.

No. Magento remains the storefront. SmartCo is used for the operational workflow behind the order where that adds value.

Yes, where the relevant APIs and business rules support it. The aim is to let each platform handle the job it is best at without re-keying the same information.

SmartCo can work alongside Web Solutions eCommerce capability, so a store and CRM can be discussed as one connected project where appropriate.

Supported SmartCo connectors do not carry a separate per-connector licence fee. Any bespoke work and third-party charges are agreed separately where needed.

Yes. Permissions are configured around the roles and responsibilities agreed for the deployment so staff only see and do what is appropriate to their work.

SmartCo workflows can record important activity and changes so the organisation has a clearer history of what happened and when. The exact audit requirements are agreed around the project.

Yes. Managed SmartCo deployments include platform maintenance and backup arrangements appropriate to the agreed hosting setup.

Yes. White-label deployment can use the client domain and branding where that is part of the chosen package.

SmartCo remains the point of contact for the managed platform. Support and future changes are handled through the ongoing client relationship rather than handing the system over and disappearing.