Access and record structure
Up to five client users and twenty custom properties establish the agreed baseline.
HubSpot Starter implementation for postsecondary teams
Build a clean HubSpot Starter foundation.
We configure a focused baseline for records, one pipeline, inquiry capture, reporting, and training for a small team with one clear operating process.
See the published scope- Price
- Starts at $3,500
- Typical elapsed time
- 2 to 3 weeks
- Delivery
- Koro-led, shared-responsibility implementation.
This price covers the published service baseline. HubSpot software and other third-party costs are separate. We confirm final scope, responsibilities, timing, and fee in writing before work begins.
Timing assumes timely access, usable source data, available decision-makers, testing, and approvals. The written scope confirms the schedule before work begins.
See whether Setup fits
Share your institution, priority, and HubSpot starting point. We’ll confirm whether the published Setup baseline fits before proposing work.
A focused operating foundation
HubSpot Solutions Partner (opens in a new tab)
The published baseline makes the main ceilings visible before the scoping conversation.
Your student information system remains the academic system of record. Setup does not replace it.
A right-sized foundation
Start with the parts your team will actually use.
Setup keeps the first implementation deliberately focused: core records, one capture path, one operating pipeline, basic reporting, training, and launch support.
Inquiry capture
One form and one HubSpot scheduling page create a focused path into HubSpot.
Operating pipeline
One pipeline with up to seven stages makes the agreed process visible.
Basic visibility
One clean import and one dashboard with up to five reports support the first operating view.
Fit and boundary
A focused foundation for one clear process.
Setup is designed for work that can stay within a clear Starter baseline. Larger automation, data, integration, or governance needs should take a different path.
Setup is useful when
- A small team with one primary operating process.
- A clean source file that is ready for one bounded import.
- A team that can make field, stage, reporting, and launch decisions promptly.
- A foundation that does not require workflows, routing, or integrations within Koro’s published Setup scope.
Choose Launch or Scale when
- You need more users, properties, pipelines, forms, reports, or data than the baseline allows.
- Routing, workflow automation, multiple Hubs, advanced migration, or integration is central to the work.
- Permissions, governance, multiple teams, or connected systems materially change the architecture.
Published starting point
The published Setup boundaries.
The written scope confirms the exact records, fields, stages, data, reports, access, responsibilities, and approval path.
Access and records
- Up to 5 users.
- Up to 20 custom properties.
Capture and operating path
- 1 pipeline with up to 7 stages.
- 1 form and 1 HubSpot scheduling page (meetings link).
Data and reporting
- 1 clean import of up to 5,000 records.
- 1 dashboard with up to 5 reports.
Training and launch support
- 1 training session of 60 to 90 minutes.
- 7 days of agreed post-launch support.
These quantities define Koro’s published service boundaries, not HubSpot product limits. “Users” means up to five client users configured within service scope. Required HubSpot seats are purchased separately.
Delivery
A bounded path from decisions to launch.
The handoff includes the agreed configured foundation, import checks, team training, and launch support. Each phase depends on decisions, access, source data, review, testing, and approval being ready when needed.
Confirm the foundation.
Agree on access, users, records, fields, stages, capture, reporting, source data, and approval ownership.
Configure the baseline.
Build the included records, pipeline, form, scheduling page, dashboard, and reports.
Import and check.
Complete the agreed clean import and review the configured path against scope.
Train and launch.
Deliver training, confirm launch approval, and begin the agreed seven-day support window.
Shared responsibility
Clear inputs. Clear ownership.
We configure the agreed foundation. Your team supplies the decisions, access, usable source data, testing, and approval that make the work possible.
Your team provides
- One accountable decision-maker.
- Timely HubSpot and source-system access through an agreed secure method.
- Approved process, field, stage, and reporting decisions.
- One clean, structured source file for the included import.
- Representative review, testing, and launch approval.
We provide
- Confirm the agreed bounded scope.
- Configure the included HubSpot foundation.
- Complete the agreed import and configuration checks.
- Deliver the included training and agreed launch support.
Koro requests access and source data only through an agreed secure method, never through this form.
Evidence in context
Foundation work should make ownership visible.
The record below shows how capture, assignment, next action, stage progression, and reporting were treated as one operating path.
See the admissions operating path.
The admissions operations page shows how capture, assignment, next action, progression, exceptions, and reporting fit into one governed path. It explains Koro's method, not a promised Setup scope or result.
Explore admissions operationsSelected founder experience. This work predates Koro Solutions. The organization is anonymized and is not represented as a Koro Solutions client, sponsor, or endorser.
Other paths
Use the service that matches the work.
Setup should stay bounded. If the work cannot, choose the path that reflects the real implementation need.
Need the decision first?
Use Plan to clarify what to buy, fix, or build before committing to implementation.
Need routing or workflow automation?
Use Launch when Professional-level automation and a connected operating process are central.
Need connected systems or governance?
Use Scale when integration, migration, multiple teams, permissions, or governance changes the architecture.
Need guidance instead of implementation?
Use onboarding and support for guided configuration or defined ongoing capacity. Use Scale when technical work changes the architecture.
Questions and boundaries
Questions about Setup.
These answers explain the published baseline, data readiness, subscription boundary, timing, and what requires a different scope.
Is $3,500 the final price?
It is the published starting point for the bounded scope shown on this page. Final scope, responsibilities, fee, and schedule are confirmed in writing before work begins.
Which HubSpot Starter subscription do we need?
The required HubSpot products and seats depend on the agreed capture, pipeline, scheduling, reporting, and user needs. We confirm the required subscription before work begins. HubSpot software is separate from Koro's service fee.
What is a clean import?
Koro reviews the proposed source during scoping. Cleanup, deduplication, transformation, multiple sources, relationship reconstruction, or unsupported data can require separate migration work.
What counts toward the 5,000-record limit?
The written scope confirms the included objects, source rows, associations, and counting method. The published ceiling does not automatically include every object, activity, attachment, history item, or source system.
What does the included form cover?
The written scope confirms the form fields, consent requirements, embed destination, styling, and testing. Website copy, page design, and custom development are not assumed by the published Setup baseline.
How is Setup different from guided onboarding?
In Setup, we configure the agreed bounded foundation. In guided onboarding, your team performs the hands-on configuration with our agreed guidance and review.
Are workflows or integrations included?
They are not part of the published Setup baseline. Use Launch when workflow automation is central. Use Scale when migration, integration, or broader connected-system work changes the architecture.
What can change the 2-to-3-week timing?
Late access, unusable source data, unavailable decision-makers, changed requirements, delayed testing, or delayed approval can change the schedule.
Is HubSpot software included?
No. HubSpot software, seats, taxes, third-party tools, and usage charges are separate unless a written proposal says otherwise.
What happens after launch?
Setup includes seven days of agreed post-launch support. Additional administration, improvement, or capacity can be scoped through Onboarding & support.
Next step
Build the right-sized foundation.
Share your institution, current HubSpot situation, and any useful process context. We’ll confirm whether Setup fits before proposing work.
Discuss Setup