Planning conversation
Plan
We are not sure what to buy, fix, or build.
A high-level recommendation, with an optional short summary.
No cost30-minute planning conversationExplore Plan
Services & pricing
Choose the right starting point for your HubSpot system.
We help postsecondary admissions and enrollment teams make the initial decision, build a focused foundation, implement a connected operating process, or scope a more complex system. Compare fit, published scope, timing, and price before you contact us.
Prices shown are for Koro professional services. HubSpot software and any HubSpot-required onboarding are separate.
Collaborative HubSpot planning
Four paths
Choose the path that fits the work in front of you.
Plan is a planning conversation. Setup, Launch, and Scale are alternative implementation paths with different starting boundaries, not required steps in a sequence.
2 to 3 weeks
Setup
We need a clean, focused HubSpot Starter foundation.
A configured bounded foundation, training, and launch support.
Starts at $3,500Published baseline highlights
- Up to 5 users and 20 custom properties.
- 1 pipeline with up to 7 stages.
- 1 clean import of up to 5,000 records.
- 1 dashboard with up to 5 reports.
30 to 45 days
Launch
We need HubSpot Professional implemented around our process.
A configured Professional operating baseline, training, and launch support.
Starts at $9,500Published baseline highlights
- Up to 15 users and 50 custom properties.
- 1 main pipeline with up to 8 stages.
- Up to 6 workflows and 3 routing rules.
- Up to 25,000 clean records.
8 to 12 weeks
Scale
Our system, data, or operating model has become complex.
A scoped complex system with agreed architecture, implementation, enablement, and support.
From $15,000Published baseline highlights
- Up to 3 selected HubSpot product Hubs, 3 pipelines, and 100 custom properties total across the included HubSpot objects.
- Up to 15 workflows total across the engagement.
- Up to 75,000 reasonably clean records.
- 1 bounded native connector configuration.
What changes scope
Implementation scope depends on the system around it.
For paid work, portal architecture, data, connections, operating design, team readiness, and enablement determine what belongs in the written scope.
HubSpot environment
Selected products, editions, portals, teams, users, pipelines, regions, and permissions.
Data
Source systems, volume, history, relationships, quality, cleanup, transformation, and identity rules.
Connections
Native availability, objects, direction, frequency, APIs, middleware, monitoring, and vendor cooperation.
Operating design
Records, stages, ownership, routing, automation, reporting, governance, and exception handling.
Enablement
Content, documentation, training, testing, adoption, and post-launch support.
Readiness
Access, available decision-makers, usable source data, testing capacity, approvals, and required timing.
Evidence in context
Verify the relationship. Review the work in context.
Partner status and operating evidence answer different questions. Both should be evaluated with their limits visible.
HubSpot Solutions Partner
Koro Solutions is listed in HubSpot's official Solutions Directory. The listing verifies the partner relationship, not a customer rating or guaranteed result.
Verify Koro on HubSpot (opens in a new tab)Selected founder experience
Review how records, ownership, handoffs, system boundaries, and reporting were considered across a connected career-college operating path.
Explore case studiesSelected founder experience. This work predates Koro Solutions. The organization is anonymized and is not represented as a Koro Solutions client, sponsor, or endorser.
Detailed comparison
Compare the published starting boundaries.
The comparison shows what distinguishes each path before written scoping. It is not a substitute for the complete service page or proposal.
| Compare | PlanView Plan details | SetupView Setup details | LaunchView Launch details | ScaleView Scale details |
|---|---|---|---|---|
| Best fit | A high-level decision before committing to a build. | One focused HubSpot Starter process. | One defined Professional operating process. | Complex HubSpot architecture or governance. |
| Price | No cost | Starts at $3,500 | Starts at $9,500 | From $15,000 |
| Typical timing | 30 minutes | 2 to 3 weeks | 30 to 45 days | 8 to 12 weeks |
| Delivery | Advisory conversation. | Koro-led, shared-responsibility implementation. | Shared implementation. Koro configures the agreed system; the client supplies decisions, data, testing, and approval. | Scoped complex implementation. |
| Users | Not included | Up to 5 | Up to 15 | Confirmed in written scope |
| Custom properties | Not included | Up to 20 | Up to 50 | Up to 100 total across included HubSpot objects |
| Pipelines | Not included | 1 pipeline, up to 7 stages | 1 main pipeline, up to 8 stages | Up to 3 pipelines |
| Inquiry capture | Not included | 1 form and 1 HubSpot scheduling page (meetings link) | Up to 3 forms and 2 meeting links | Confirmed in written scope |
| Automation | Not included | Not included in the published baseline | Up to 3 routing rules, 6 workflows, and 5 active lists | Up to 15 workflows total across the engagement |
| Data | No data work | 1 clean import, up to 5,000 records | 1 clean import, up to 25,000 records | Up to 75,000 reasonably clean records |
| Reporting | Not included | 1 dashboard, up to 5 reports | Up to 2 dashboards and 12 reports | Up to 3 dashboards and 25 reports total across the engagement |
| Integrations | No integration review | Not included in the published baseline | Not included in the published baseline | 1 bounded native connector configuration |
| Training | Not included | 1 session, 60 to 90 minutes | Admin and team training | Up to 4 training sessions; details defined in writing |
| Post-launch support | Not applicable | 7 days of agreed support | 30 days of agreed support | 45 days of agreed support; clock and work defined in writing |
Plan
- Best fit
- A high-level decision before committing to a build.
- Price
- No cost
- Typical timing
- 30 minutes
View full Plan comparison
- Delivery
- Advisory conversation.
- Users
- Not included
- Custom properties
- Not included
- Pipelines
- Not included
- Inquiry capture
- Not included
- Automation
- Not included
- Data
- No data work
- Reporting
- Not included
- Integrations
- No integration review
- Training
- Not included
- Post-launch support
- Not applicable
Setup
- Best fit
- One focused HubSpot Starter process.
- Price
- Starts at $3,500
- Typical timing
- 2 to 3 weeks
View full Setup comparison
- Delivery
- Koro-led, shared-responsibility implementation.
- Users
- Up to 5
- Custom properties
- Up to 20
- Pipelines
- 1 pipeline, up to 7 stages
- Inquiry capture
- 1 form and 1 HubSpot scheduling page (meetings link)
- Automation
- Not included in the published baseline
- Data
- 1 clean import, up to 5,000 records
- Reporting
- 1 dashboard, up to 5 reports
- Integrations
- Not included in the published baseline
- Training
- 1 session, 60 to 90 minutes
- Post-launch support
- 7 days of agreed support
Launch
- Best fit
- One defined Professional operating process.
- Price
- Starts at $9,500
- Typical timing
- 30 to 45 days
View full Launch comparison
- Delivery
- Shared implementation. Koro configures the agreed system; the client supplies decisions, data, testing, and approval.
- Users
- Up to 15
- Custom properties
- Up to 50
- Pipelines
- 1 main pipeline, up to 8 stages
- Inquiry capture
- Up to 3 forms and 2 meeting links
- Automation
- Up to 3 routing rules, 6 workflows, and 5 active lists
- Data
- 1 clean import, up to 25,000 records
- Reporting
- Up to 2 dashboards and 12 reports
- Integrations
- Not included in the published baseline
- Training
- Admin and team training
- Post-launch support
- 30 days of agreed support
Scale
- Best fit
- Complex HubSpot architecture or governance.
- Price
- From $15,000
- Typical timing
- 8 to 12 weeks
View full Scale comparison
- Delivery
- Scoped complex implementation.
- Users
- Confirmed in written scope
- Custom properties
- Up to 100 total across included HubSpot objects
- Pipelines
- Up to 3 pipelines
- Inquiry capture
- Confirmed in written scope
- Automation
- Up to 15 workflows total across the engagement
- Data
- Up to 75,000 reasonably clean records
- Reporting
- Up to 3 dashboards and 25 reports total across the engagement
- Integrations
- 1 bounded native connector configuration
- Training
- Up to 4 training sessions; details defined in writing
- Post-launch support
- 45 days of agreed support; clock and work defined in writing
Still deciding?
Not ready to commit to a build? Start with Plan.
One focused conversation can clarify the likely path. Plan is high-level guidance, not a portal audit or implementation blueprint.
Onboarding & support
Guidance before launch. Defined capacity after launch.
Choose guided onboarding when your team will perform the configuration, or ongoing support when an operating portal needs defined administration and improvement capacity.
Guided onboarding
Starts at $1,500Your team configures HubSpot with Koro's agreed guidance and review.
View Guided onboarding detailsOngoing support
Starts at $1,500/monthDefined monthly capacity for agreed administration and improvement priorities.
View Ongoing support detailsThe full service page explains delivery ownership, work boundaries, capacity, active-request limits, and pricing.
Compare Onboarding & supportWhat happens next
Scoping should make the decision clearer.
Contacting Koro is not an order. It begins a bounded process for confirming fit, responsibilities, timing, and commercial terms.
Share the starting point
Tell us about the institution, current HubSpot state, operating problem, and decision in front of you.
OutputInstitution, system state, problem, and decision.
Clarify fit and readiness
We test the likely service path, material scope drivers, client inputs, and unresolved dependencies.
OutputLikely path and remaining questions.
Document the proposed work
When paid work fits, Koro puts the proposed scope, responsibilities, fee, timing, assumptions, and exclusions in writing.
OutputA written proposal or defined next step.
Confirm before work begins
The engagement starts only after both sides agree to the applicable written scope and terms.
OutputAgreed work and accountable owners.
Questions and boundaries
Commercial questions should have direct answers.
Software, onboarding, scope changes, migration, support, responsibilities, and controlling terms.
Is HubSpot software included?
No. Prices shown are for Koro professional services. HubSpot software, any HubSpot-required onboarding, taxes, third-party tools, and usage charges are separate unless a written proposal says otherwise.
Can Koro replace or waive HubSpot-required onboarding?
HubSpot determines any required onboarding for the products and transaction. We confirm the applicable requirement during scoping and do not promise that Koro services replace it.
How is Plan different from guided onboarding?
Plan is a no-cost 30-minute, high-level planning conversation. Guided onboarding is a paid, scoped service in which your team performs the hands-on configuration with Koro's agreed guidance and review.
What changes the final fee?
Selected Hubs, users, pipelines, source systems, data quality and volume, migration, integrations, automation, reporting, permissions, governance, content, enablement, readiness, and timing can change scope and fee.
How are scope changes handled?
The applicable signed client documents control scope changes. Work outside the agreed boundary is confirmed in writing before Koro treats it as included.
What does our team need to provide?
The exact responsibilities depend on the service. Common inputs include an accountable decision-maker, system access, process decisions, usable source data, content, representative testing, and timely approvals.
How are migration and integration work handled?
Migration and integration work is separate unless the written scope includes it. Scale's published starting boundary can encompass one bounded native connector configuration; it is not automatically included in every Scale engagement. Other migration and integration work is scoped by source, objects, history, mappings, data quality, connector or API limits, testing, and cutover requirements.
What support is included after launch?
Setup includes 7 days, Launch includes 30 days, and Scale includes 45 days of agreed post-launch support. The written scope defines the covered work. Continued administration or improvement capacity can be scoped through ongoing support.
What controls payment, rescheduling, cancellation, and refund terms?
The applicable signed client documents control those terms. The website does not create or change them.
Next step
Start with the system you have now.
Tell us where you are now and what needs to change. We will use a focused conversation to confirm fit, then put any proposed scope, responsibilities, timing, and fee in writing.