Control at scale.

No. It is the published starting point for an engagement that fits the Scale categories and ceilings on this page. Architecture, data, migration, integration, governance, testing, enablement, readiness, and timing can change the final scope, fee, and schedule. We confirm them in writing before work begins.

It is a planning range for a typical Koro Scale engagement. It is not a bank of hours, an hourly entitlement, or a promise that every engagement uses that amount. The signed scope controls the work, responsibilities, fee, schedule, assumptions, and change process.

Not in every case. Scale is intended for complex environments using the Professional- or Enterprise-tier HubSpot products required for the agreed scope. The required products, editions, seats, add-ons, capabilities, and onboarding requirements depend on the agreed records, permissions, automation, reporting, data, and integration work. We confirm them during architecture and scoping.

It means up to three selected HubSpot product Hubs within the written architecture, not three separate portals. The exact products, editions, seats, features, and work included for each Hub are confirmed in scope. Additional portals or broader product work are separate unless included in writing.

It means configuration and testing of one available native connector within the exact application, objects, direction, settings, ownership, and dependency limits defined in writing. Custom mapping, middleware, custom APIs, and source-system remediation are separate unless expressly included.

Not in the published Scale baseline. They can be evaluated and scoped separately when the architecture requires them. API access, vendor cooperation, middleware, usage, hosting, monitoring, security review, maintenance, and third-party development can affect feasibility, responsibility, fee, and timing.

The written scope confirms the included objects, rows, relationships, history, sources, associations, and counting method. Extensive cleanup, deduplication, transformation, unsupported data, attachments, activity history, relationship reconstruction, or multiple source systems can require separate migration work.

Choose Launch when one defined process can fit within its published operating, data, automation, reporting, and enablement boundary. Choose Scale when multiple Hubs, pipelines, teams, systems, permissions, migration, integration, governance, or custom technical work materially changes the architecture.

Scale normally requires an accountable sponsor or decision-maker plus the relevant process, data, system, security, and technical owners. Your team also provides secure access, source-system expertise, representative testing, user acceptance, and timely written approvals.

Access, source-data condition, architecture decisions, content, product licensing, vendor cooperation, connector or API limitations, testing, approval, and changes to the agreed scope can affect timing. The period runs through approved launch. The 45-day support window begins after launch.

No. HubSpot is not positioned as the academic system of record. It can support agreed relationship and operating work around the institution's processes. The SIS and other authoritative learning, financial, payment, and document systems retain the responsibilities defined for them in the written architecture.

No. Koro does not represent Scale as a FERPA, privacy, security, accounting, regulatory, or other compliance certification. Applicable requirements, product capabilities, access methods, data handling, legal review, security review, and organizational responsibilities must be defined by the appropriate parties.

The written scope defines the work covered during the agreed post-launch period. Continued administration, optimization, technical capacity, or improvement can be scoped separately through ongoing support or another written engagement.