Plans Only
Best when you need documentation for review, feasibility, local conversations, or early planning.
The decision: plans-only or EasyKit
The right path depends on project maturity. If the model, site, local requirements, and local team are still unclear, a plan package may be the safer next step. If the model is selected, local review is underway, and the project is moving toward execution, EasyKit may become relevant.
Plans now, EasyKit later
Best when you expect prefabrication but need to confirm model, site, local rules, and scope first.
EasyKit Core
Best when the project has a clearer model and a capable local team, and you want an essential prefabricated scope.
EasyKit Extended
Best when you want a broader prefabricated package and stronger coordination, while still keeping local responsibilities clear.
When Plans Only is the right path
Plans Only can be the correct choice when the project needs clarity before larger commitments. This path helps you understand the model, talk to local professionals, and prepare better decisions without moving too early into kit scope.
You are still testing feasibility
Use plans to understand whether the model direction makes sense.
You need local consultant feedback
Engineers, architects, authorities, or builders can review the project direction.
You do not have a final site
Plans may help early thinking, but site-specific decisions remain open.
You are comparing models
A plan package can help you move from visual preference to project logic.
You are not ready for delivery
EasyKit delivery requires access, unloading, storage, and site readiness.
You want a lower first commitment
Plans are a controlled first commercial step before larger package decisions.
When EasyKit makes sense
EasyKit becomes more meaningful when the model, documentation, site, local review, and local team are clearer. It should not be treated as a generic price request before the project has enough definition.
Model selected
The selected model controls the package scope.
Plan package started or planned
Documentation gives the project a stronger basis.
Site direction known
Destination, access, foundation, unloading, and storage must be reviewed.
Local team identified
Builders, engineers, and local professionals remain essential.
Local responsibilities understood
Permits, foundation, MEP, labour, tools, and inspections are not automatically included.
Budget direction realistic
EasyKit is only one part of total project cost.
Plans now, EasyKit later
Many clients should follow a staged path: choose a model, buy the right plan package, review local requirements, then request EasyKit guidance when the project is clearer. This avoids vague quote requests and reduces the risk of choosing the wrong package too early.
Choose the model
Start with the model that fits use, site, and build path.
Choose the plan package
Use Planning Information or Complete Project depending on project stage.
Review locally
Discuss permits, engineering, foundation, MEP, site access, and local costs.
Decide EasyKit scope
Choose Core or Extended only after responsibilities are clearer.
Add support if needed
Remote, Checkpoint, or Dedicated Assembly Support can help the local team.
When you are not ready for either
Sometimes the smartest decision is to pause before buying anything. You may need more clarity before choosing plans or EasyKit.
You do not know the use case
Home, guest house, rental, retreat, cabin, or hospitality use can change requirements.
You have no model direction
Start with Model Series or Browse Models.
You have no site direction
Local rules and site conditions may control the decision.
You expect turnkey delivery
SoletaHousePlans is not selling a finished turnkey local construction package.
You do not understand local responsibilities
Permits, engineering, foundation, MEP, labour, tools, and inspections remain local.
You only want a quick kit price
A meaningful EasyKit quote needs model, scope, destination, access, and project context.
Responsibility split
Plans and EasyKit help different parts of the project. Local responsibilities remain local unless a verified package says otherwise.
Soleta plan packages may help with
- model understanding
- documentation basis
- local conversations
- project-stage clarity
- EasyKit preparation
- next-step recommendations
EasyKit may help with
- prepared package scope
- GLULAM structural logic
- component organization
- package coordination
- delivery preparation
- assembly documentation
Local team remains responsible for
- permits and approvals
- local engineering
- foundation and site work
- MEP and utilities
- local labour and tools
- safety and supervision
- unloading and storage
- inspections and compliance
Compare the paths
Best for
Plans Only
early review
Plans Now + EasyKit Later
staged path
EasyKit Path
prefabrication readiness
Model selected
Plans Only
recommended
Plans Now + EasyKit Later
strongly recommended
EasyKit Path
required for meaningful quote
Plan package
Plans Only
main product
Plans Now + EasyKit Later
first step
EasyKit Path
strongly recommended
EasyKit scope
Plans Only
not selected
Plans Now + EasyKit Later
later
EasyKit Path
Core or Extended
Local review
Plans Only
needed
Plans Now + EasyKit Later
needed before EasyKit
EasyKit Path
needed before execution
Delivery planning
Plans Only
not yet
Plans Now + EasyKit Later
later
EasyKit Path
required
Local team
Plans Only
not always selected
Plans Now + EasyKit Later
should be identified
EasyKit Path
required
Budget clarity
Plans Only
early direction
Plans Now + EasyKit Later
improving
EasyKit Path
more serious
Checkout status
Plans Only
preview only
Plans Now + EasyKit Later
preview only
EasyKit Path
quote required
Risk level
Plans Only
lower commitment
Plans Now + EasyKit Later
staged
EasyKit Path
higher commitment
EasyKit readiness checklist
Before requesting EasyKit seriously, try to answer these questions.
- Which Soleta model is selected or strongly shortlisted?
- Which plan package do you have or plan to buy?
- What is the project country and approximate site location?
- Is the plot owned, shortlisted, or still unknown?
- Are local rules known or under review?
- Who handles local engineering?
- Who handles foundation design and construction?
- Who handles MEP and utilities?
- Is site access suitable for delivery?
- Is unloading and storage planned?
- Is a local assembly team identified?
- Do you need Remote, Checkpoint, or Dedicated Assembly Support?
Future decision map
IMAGE PLACEHOLDER
Recommended content: visual decision map showing Plans Only, Plans Now + EasyKit Later, EasyKit Core, EasyKit Extended, Delivery, and Assembly Support with arrows and responsibility notes.
Recommended aspect ratio: 16:9. Purpose: show how future visual guidance will explain the full decision path.
Decision preview
Selected model
No model selected yet.
Plan package
No plan package selected yet.
EasyKit interest
Not selected yet.
Local readiness
Not reviewed yet.
Recommended path
Start with model and plan package before requesting EasyKit.
Common mistakes when choosing between plans and EasyKit
The selected model controls the package scope.
Plans create the basis for local review and serious decisions.
EasyKit does not replace local labour, permits, foundation, MEP, or site supervision.
EasyKit requires access, unloading, storage, and site preparation.
Core or Extended should be selected after model, site, local review, and responsibilities are clearer.
Local rules, engineering, foundation, and utilities must be reviewed locally.
Plans or EasyKit FAQ
Should I buy plans before EasyKit?
In most cases, yes. Plans help clarify model, documentation, local review, and scope before EasyKit discussions.
Can I buy EasyKit without a plan package?
The recommended path is to start with the relevant plan package. EasyKit scope is difficult to define without enough documentation.
Is Plans Only a complete project path?
It can be a valid path for clients who want documentation and local execution, but local professionals must still confirm what is required.
Is EasyKit a complete house?
No. EasyKit is a prefabricated package path, not turnkey local construction.
Can I start with Planning Information and upgrade later?
Upgrade or credit policy is to be confirmed before checkout.
Which is safer: Core or Extended?
Neither is universally safer. The right choice depends on model, site, local team, budget, scope, and risk tolerance.
What if I do not know?
Use the staged path: choose a model, choose a plan package, review locally, then request guidance.
Ready to choose your next step?
Do not rush into the largest package. Start with the model and documentation depth that fit your project stage, then move toward EasyKit when the local path is clearer.