Included boundary
Koro guidance for the agreed Hub count and priorities. The written scope confirms work areas, responsibilities, sessions, review points, and outputs.
Onboarding & support
Choose guided, ongoing, migration, or integration support.
Use this path when your team needs focused help without a full Setup, Launch, or Scale implementation. Each service states who executes and what determines scope.
Choose by need
Start with the help you need.
Who performs the work and what unit bounds the service are visible before you choose a path.
- View service
Guide our team
Your team configures HubSpot with Koro's agreed guidance.
- View service
Provide ongoing capacity
Koro works through agreed priorities within monthly hours and active-request limits.
- View service
Move our data
Koro scopes a standalone migration by source and data complexity.
- View service
Connect a system
Koro scopes a native connection, data sync, custom API, or more complex system integration.
Guided onboarding
Guide our team through onboarding.
- Best fit
- A team that wants to retain hands-on configuration ownership and needs direction for the agreed Hub count and priorities.
- Outcome
- A clearer onboarding path, with client execution and Koro guidance defined in writing.
- Delivery
- Guided. Your team performs the hands-on configuration. Koro provides the agreed direction and review.
| Scope | Price | Execution | Duration |
|---|---|---|---|
| 1 Hub | $1,500 | Client configuration with Koro guidance | Confirmed during scoping |
| 2 Hubs | $2,500 | Client configuration with Koro guidance | Confirmed during scoping |
| 3 Hubs | $3,500 | Client configuration with Koro guidance | Confirmed during scoping |
| Enterprise or custom | From $4,500 | Confirmed during scoping | Confirmed during scoping |
Separate work
Done-for-you configuration, migration, integration, custom code, extensive data cleanup, ongoing administration, and work outside the agreed priorities are separate.
Process
Confirm the Hub count and owner, work through agreed topics, complete client-owned configuration and testing, then review the work and next step.
Koro Care
Add defined capacity after or outside a project.
- Best fit
- A team with an operating HubSpot system and a continuing queue of agreed administration, reporting, automation, or improvement work.
- Outcome
- Prioritized work completed within a visible monthly capacity and concurrent active-request limit.
- Delivery
- Ongoing, capacity-based service.
| Plan | Price | Monthly capacity | Active requests | Cadence |
|---|---|---|---|---|
| Lite | $1,500/month | Up to 5 hours | 1 active request | Monthly |
| Growth | $3,000/month | Up to 12 hours | 2 active requests | Biweekly |
| RevOps | $5,000/month | Up to 25 hours | 3 active requests | Weekly |
| Enterprise | From $7,500/month | Custom capacity | Custom | Confirmed during scoping |
Included boundary
Work is selected from the agreed priority queue and completed within the plan's monthly capacity and concurrent-request limit.
Separate work
Large implementations, migrations, integrations, custom software, urgent service levels, work beyond capacity, and rollover are not implied.
Process
Confirm eligible work and capacity, prioritize requests, complete work within available capacity, then use the stated cadence to review what comes next.
The linked record is relevant to phased rollout, training, exceptions, and production refinement. It does not document a Koro Care retainer, response time, or throughput result.
Read the production-refinement recordSelected founder experience. This work predates Koro Solutions. The organization is anonymized and is not represented as a Koro Solutions client, sponsor, or endorser.Migration services
Move agreed data with the source and risk in view.
- Best fit
- The target operating architecture is already settled and the primary need is to move agreed data into HubSpot.
- Outcome
- An agreed migration path for the named sources, records, mappings, validation, and cutover responsibilities.
- Delivery
- Scoped technical service.
| Migration path | Price | Duration |
|---|---|---|
| Clean CSV | From $1,500 | Confirmed during scoping |
| Spreadsheet sources | From $3,500 | Confirmed during scoping |
| Standard CRM | From $7,500 | Confirmed during scoping |
| Complex migration | From $15,000 | Confirmed during scoping |
| Multiple systems | From $25,000 or custom | Confirmed during scoping |
Included boundary
Only the sources, objects, relationships, history, mappings, transformations, validation steps, and cutover responsibilities named in writing.
Separate work
Additional sources, extensive cleanup, unsupported objects, assets, historical reconstruction, custom transformation, integration, and middleware.
Process
Confirm source and target, agree mappings and validation, complete the scoped migration sequence, then support client validation and cutover approval.
Integration services
Connect systems with ownership defined.
- Best fit
- The operating architecture is already settled and the primary need is a bounded connection between HubSpot and another system.
- Outcome
- An agreed connection with named systems, objects, direction, mappings, validation, and ownership.
- Delivery
- Scoped technical service.
| Integration path | Price | Duration |
|---|---|---|
| Native app connection | From $1,000 | Confirmed during scoping |
| Native app plus workflow | From $2,500 | Confirmed during scoping |
| One-way integration | From $5,000 | Confirmed during scoping |
| Two-way integration | From $8,500 | Confirmed during scoping |
| Custom API integration | From $12,500 | Confirmed during scoping |
| ERP, accounting, or payment system | From $15,000 | Confirmed during scoping |
Included boundary
Only the applications, objects, fields, direction, frequency, mappings, workflow behavior, validation, and ownership named in writing.
Separate work
Middleware, custom software, expanded mappings, historical remediation, additional systems, extended monitoring, security review, and vendor work.
Process
Confirm capability and dependencies, agree mappings and conflict rules, complete the connection, then support client validation and activation approval.
The linked record documents authoritative-system boundaries, approvals, exceptions, and traceability. It is not a HubSpot implementation case or evidence of a Koro integration result.
Read the systems-traceability recordSelected founder experience. This work predates Koro Solutions. The organization is anonymized and is not represented as a Koro Solutions client, sponsor, or endorser.Scope and readiness
Focused work still needs a defined boundary.
Do not send passwords, credentials, student records, or other sensitive data through the inquiry form. We confirm an appropriate access method only after the work and responsibilities are defined.
Data movement
Sources, objects, relationships, history, attachments, quality, transformations, validation, and cutover.
System connection
Native availability, APIs, objects, mappings, direction, frequency, conflict handling, monitoring, and vendor cooperation.
Delivery readiness
Authorized access, internal owners, business rules, representative testing, written approval, and realistic timing.
Your team provides
- One accountable owner who can prioritize work and make timely decisions.
- Appropriate access through an agreed secure method.
- Complete process, data, system, and acceptance context for the agreed work.
- Timely review, representative testing, and approval.
Questions and boundaries
Questions about onboarding and support.
Direct answers about execution ownership, monthly capacity, technical scope, and controlling terms.
How is guided onboarding different from Setup?
In guided onboarding, your team performs the hands-on configuration with Koro's agreed guidance. In Setup, Koro configures the agreed bounded foundation.
Does Koro Care mean unlimited work?
No. Each plan has monthly hours and an active-request limit. The written scope defines eligible work and any additional-capacity or rollover terms.
Does meeting cadence mean response time?
No. Monthly, biweekly, or weekly cadence describes the working rhythm. It does not create a response-time commitment or service-level agreement.
What changes migration pricing?
Source count, objects, relationships, history, attachments, mappings, data quality, transformation, validation, and cutover requirements can change scope and price.
What changes integration pricing?
Native availability, API access, objects, mappings, direction, frequency, conflict handling, middleware, monitoring, security, testing, and vendor cooperation can change scope and price.
When does standalone technical work become Scale?
Use Scale when migration or integration materially changes the operating architecture, records, process, permissions, reporting, training, or governance.
Are HubSpot and third-party charges included?
No. HubSpot software, any HubSpot-required onboarding, taxes, third-party tools, vendor charges, usage charges, and middleware are separate unless a written proposal says otherwise.
What are the payment, term, cancellation, or rollover rules?
The applicable signed client documents control those terms. The website does not create or change them.
Next step
Bring us the need, not a guessed package.
Tell us whether you need guidance, ongoing capacity, data movement, or a system connection. We will confirm the appropriate path and put any proposed scope, responsibilities, timing, and fee in writing.