Step 1
Choose or shortlist the model
The model controls the documentation and package path.
The simple sequence
The safest Soleta path usually follows a clear order. Skipping steps may create vague quotes, wrong package choices, or unrealistic expectations.
Step 2
Choose the plan package
Planning Information or Complete Project depends on project stage.
Step 3
Review local requirements
Permits, engineering, foundation, MEP, and local rules must be checked locally.
Step 4
Decide Plans Only or EasyKit
Some clients stay plans-only. Others move toward EasyKit after review.
Step 5
Prepare delivery and assembly
Access, unloading, storage, local team, and support level must be planned.
Step 6
Request guidance when unclear
If the path is not obvious, ask before buying the wrong product.
What plan packages do
Plan packages give your project a documentation basis. They help you understand the model, discuss the project locally, ask better questions, and decide whether to stay plans-only or move toward EasyKit.
Planning Information Package
Early-stage review, model understanding, local conversations, feasibility questions, and budget direction.
Complete Project Package
Stronger documentation base for local review, contractor input, EasyKit inquiry, and coordination.
Local discussion basis
Plans help local professionals understand the model and identify what must be adapted or reviewed.
Not a local permit guarantee
Local authorities and professionals define what documents, signatures, and calculations are required.
What EasyKit does
EasyKit is the prefabricated package path. It can help organize key building components, GLULAM structure, package coordination, delivery preparation, and assembly documentation. EasyKit Core and EasyKit Extended differ by verified scope.
EasyKit Core
Essential prefabricated starting point for local assembly, subject to model and verified scope.
EasyKit Extended
Broader prefabricated scope for projects needing more package coordination.
GLULAM structure
GLULAM structural logic that supports premium expression and prefabrication.
Delivery and support
Delivery readiness and assembly support become important after model and package scope are clearer.
Why plans usually come before EasyKit
A meaningful EasyKit discussion needs more than enthusiasm. It needs a selected or strongly shortlisted model, the right documentation stage, destination, site context, local review direction, delivery assumptions, and local team information.
The model controls the kit
Without a model, package scope is vague.
Documentation clarifies scope
Plans reduce ambiguity before EasyKit conversations.
Local rules may change the path
Permits, engineering, foundation, and use-specific rules can affect feasibility.
Delivery needs real data
Destination, access, unloading, storage, and logistics matter.
Local team must be considered
EasyKit still requires capable local execution.
Budget must be split correctly
EasyKit is only one part of total project cost.
Plans Only vs EasyKit vs staged path
Best for
- Plans Only
- documentation and review
- EasyKit Path
- prefabrication readiness
- Plans Now + EasyKit Later
- safest staged progress
Model selection
- Plans Only
- recommended
- EasyKit Path
- required for serious quote
- Plans Now + EasyKit Later
- recommended first
Plan package
- Plans Only
- main product
- EasyKit Path
- strongly recommended
- Plans Now + EasyKit Later
- first step
Local review
- Plans Only
- required
- EasyKit Path
- required
- Plans Now + EasyKit Later
- required before EasyKit
EasyKit scope
- Plans Only
- not selected
- EasyKit Path
- Core or Extended
- Plans Now + EasyKit Later
- later decision
Delivery planning
- Plans Only
- not yet
- EasyKit Path
- required
- Plans Now + EasyKit Later
- later
Local team
- Plans Only
- useful
- EasyKit Path
- required
- Plans Now + EasyKit Later
- identify during review
Budget clarity
- Plans Only
- early direction
- EasyKit Path
- more serious
- Plans Now + EasyKit Later
- improves over time
Commitment level
- Plans Only
- lower
- EasyKit Path
- higher
- Plans Now + EasyKit Later
- controlled
Turnkey construction
- Plans Only
- not included
- EasyKit Path
- not included
- Plans Now + EasyKit Later
- not included
What remains local
Neither plans nor EasyKit remove local project responsibilities unless a verified package says otherwise.
Permits and approvals
Local authorities define what is required.
Engineering
Structure, loads, climate, foundation, and code compliance need local review.
Foundation and site work
Soil, slope, drainage, frost, bearing, and preparation are site-specific.
MEP and utilities
Electricity, plumbing, heating, cooling, ventilation, water, sewage, and drainage remain local.
Labour and supervision
Local builders, site safety, tools, lifting, and inspections remain local.
Delivery handling
Access, unloading, storage, weather protection, and local logistics must be prepared.
Cost categories to separate
A plan price or EasyKit placeholder is not the same as total project cost. Keep cost categories separate from the start.
Plan package
Planning Information or Complete Project.
EasyKit package
Core or Extended, subject to model and verified scope.
Delivery and logistics
Transport, route, unloading, storage, customs, and taxes where applicable.
Foundation and site preparation
Soil, excavation, drainage, foundation, access, and staging.
MEP and utilities
Electricity, water, sewage, heating, cooling, ventilation, and connections.
Local labour
Builders, assembly team, supervision, tools, and safety.
Permits and professionals
Local engineers, architects, surveyors, inspectors, authorities, and signatures.
Finishes and exterior works
Interior finishes, terraces, landscaping, paths, drainage, and final works.
How to prepare a better inquiry
A stronger inquiry reduces back-and-forth and helps Soleta guide the next step.
- selected or shortlisted model
- project country and approximate region
- intended use
- plot status
- site condition
- local rules known, unknown, or under review
- preferred plan package or uncertainty
- EasyKit interest: Core, Extended, unsure, or not relevant
- local team status
- delivery access known or unknown
- budget direction
- timeline direction
Do not read images as package scope
Future images, renders, lifestyle scenes, and placeholders may show furniture, terraces, landscaping, lighting, finishes, paths, accessories, or site features. These visuals help explain atmosphere and use, but they do not define what is included in Plans or EasyKit.
Image is not scope
A visual scene is not a delivery list.
Furniture and styling
Furniture, decor, appliances, lighting, and styling are not automatically included.
Site and landscape
Paths, terraces, grading, landscaping, drainage, and exterior works remain local unless verified.
Final package rules
Only verified package content defines what is included.
Future visual guide
Related products and resources
Plan package - preview
Planning Information Package
Indicative placeholder price
EUR 1,000-EUR 1,500
Plan package - preview
Complete Project Package
Indicative placeholder price
EUR 2,000-EUR 3,000
Prefabrication package - preview
EasyKit Core
Indicative placeholder price
EUR 25,000-EUR 55,000
Digital guide - preview
Plans & EasyKit Guide
Indicative placeholder price
EUR 49 / placeholder
Common mistakes about plans and EasyKit
1
Asking for EasyKit pricing too early
A useful quote needs model, scope, destination, site, and local context.
2
Treating plans as optional
Plans are often the first serious step toward local review and EasyKit clarity.
3
Confusing EasyKit with turnkey
EasyKit is not complete local construction.
4
Ignoring local costs
Foundation, MEP, labour, permits, delivery handling, and finishes can be substantial.
5
Assuming images show what is included
Only verified package content defines scope.
6
Skipping local professionals
Local engineering, permits, foundation, utilities, and inspections remain essential.
Plans & EasyKit Guide FAQ
Do I need plans before EasyKit?
In most cases, yes. Plans create a better basis for local review and EasyKit discussions.
Can I stay Plans Only?
Yes. Plans Only can be a valid path for clients who want documentation and local execution without immediate EasyKit.
Is EasyKit a complete house?
No. EasyKit is a prefabricated package path, not turnkey local construction.
Does EasyKit include foundation or MEP?
No. Foundation, mechanical, electrical, plumbing, utilities, heating, cooling, ventilation, and drainage are usually local responsibilities unless verified otherwise.
Can I start with Planning Information and move to EasyKit later?
Yes, that is often a sensible staged path. Upgrade or credit policies are to be confirmed before checkout.
Are prices final?
No. Current prices are indicative placeholders until final package scope and commercial policies are verified.
What should I do if I am unsure?
Choose or shortlist a model, compare plan packages, review local requirements, then request guidance.
Final CTA
Ready to connect plans and EasyKit correctly?
Start with the model and the right documentation depth. Move toward EasyKit only when the local path, site, responsibilities, and package scope are clearer.