Landscape architecture · Site research
For homeowners, architects and developers planning a garden, courtyard or larger landscape. You bring the project question, the site and the files you already have. We check what can safely be used, study the sun, climate, terrain and setting, and give you a clear design direction — a short summary you can read in minutes, with the full technical evidence for your team.
Real site data · A landscape architect's judgment · Nothing sent without a person deciding · See what you receive
Real output · DEMO project — studio renderer, synthetic site, real public data
Illustrative deliverable anatomy — no client data
The film
Sixty seconds on what TwinzWorks does: open data read for one site, the T0 to T4 books built from it, and the landscape architect who decides what is delivered. Made with the studio's own DEMO outputs.
Studio film · DEMO projects, synthetic sites, real public data · no client data
Narrated, with captions. T is Tuncer, Z is Zümra — the two names behind TwinzWorks.
Real data, in motion
Sixteen clear months of Copernicus Sentinel-2 imagery over a DEMO site (July 2025 to October 2026), read from open archives — true colour beside the vegetation signal — and every page of the brief built from that data. Where suitable satellite or aerial imagery exists for your site it is used the same way; where it does not, the study says so. No client data.
Real output · DEMO project — studio renderer, synthetic site, real public data
16 months of Sentinel-2 (10 m), July 2025 to October 2026 — contains modified Copernicus Sentinel data.
Every package from T0 to T4 — real pages from the studio renderer, built from that data.
Behind the work
Real screens from our internal workspace, recorded on a DEMO project. Files, research, checks and delivery stay together, so nothing is lost between the site, the design and you.
Real screen of our workspace · DEMO project, no client data
01 Every project: package, brand, language and next action in one place
02 Evidence with source, method, period and scale
03 Technical QA kept separate from professional review
04 Controlled delivery with rights and review state
In four questions
The project question, the site, and the files you already have.
We verify the inputs that can safely be used, study the site and turn the findings into a design direction — with a named human review before anything is sent.
A short visual summary for you, plus books, plans, schedules and spatial files for your team — scoped to your project.
Ask for a site survey, approve a concept, ask for a revision, or take delivery.
Three ways to start
Each goal leads to a different package. Pick the one that matches the problem you have now.
If this path fits you confirm it in the guide →
If this path fits you confirm it in the guide →
If this path fits you confirm it in the guide →
Inside a delivery
Depending on scope, one project becomes a short summary for you and a set of documents, schedules and spatial files for your team. Each keeps a different part of the decision usable.
Real output · DEMO project — studio renderer, synthetic site, real public data
Real output · DEMO project — studio renderer, synthetic site, real public data
PDF / XLSX / GPKG / CAD-GIS / visual set — only within the relevant scope.
Customer journey
From the first file to the final delivery, you see what has happened, what is still missing and what comes next.
This is the decision the site needs to support.
Your files are received — and checked before they are used.
The study is being built; anything still missing stays visible.
Corrections are explained in plain words, and every version is kept.
Your approved, labelled package is ready.
Illustrative workflow for selected engagements
Accepted demonstration — no client data
Files received safely.
The upload is attached to this demonstration project and will be checked before it is used.
Type of request
Replace or update a file
What is needed
Please upload the issued scaled base plan with a visible revision date. Visual direction can continue, but scaled placement remains unavailable.
In the live portal, this sends the correction request.
Who does what
Two people, two responsibilities. The landscape decision is human; our tools keep every step of it traceable from the first file to delivery.
Landscape Architect & Design Lead
Reads your brief, sets the landscape direction, chooses planting, materials, water and visual language, reviews proposed visuals, and decides what is sent to you.
One decision, end to end
Data & Technology Lead
Builds the research and delivery tools, checks the data behind every study, and looks after privacy, rights, file quality and white-label delivery.
AI helps with research and first drafts; the landscape decision and what is sent to you stay with a named person.
Our internal tools are not what you buy; they are the spine that keeps the work from getting lost.
Honest limits
Public data describes the setting, not a survey of your garden. Satellite or aerial imagery is used only where suitable data exists for your site. A proposed visual is not a built result.
Public context ≠ survey · Proposed ≠ built · Client approval ≠ public eligibility
Labels are not interchangeable.
Start here
Email us the site, the files you already have and the decision you need to make. We will suggest the lightest scope that answers it.