TWINZWORKS

Landscape intelligence + design delivery

Turn your site and project files into landscape decisions you can act on.

You bring the project question, the site and the files you already have. TwinzWorks verifies the inputs that can safely be used, turns them into a reviewed landscape decision, and delivers the reports, plans, schedules and spatial files your project can act on.

Discuss your project Find your starting point

Reviewed site reading · Landscape design judgment · Controlled delivery · See the delivery anatomy

Illustrative deliverable anatomy — no client data

  1. Visual Site Intelligence Brief PDF · 10–16 pages
  2. Opportunity Map Plan
  3. Plant & Water Schedule XLSX
  4. Spatial Data Package GeoPackage (.gpkg)
  5. Source, Method & QA Record Included with delivery
  • Named landscape review by Zümra Timur
  • Source, method, rights and delivery limits are recorded

The whole idea in four questions

One reviewed project, four clear answers.

  1. What do you bring?

    The project question, the site, and the files you already have.

  2. What do we do?

    We verify the inputs that can safely be used, then join the evidence and the landscape decision — with a named human review.

  3. What do you receive?

    Books, plans, schedules, spatial files and registers — scoped to your project.

  4. What can you decide?

    Request a survey, approve a concept, move into coordination, ask for a revision, or take delivery.

Three client paths

Three ways in — start from your goal, not a tier code.

Each path maps to specific packages. There are no six equal cards to compare; start from the problem you actually have.

Extend your studio

Problem
Client demand for landscape work outpaces your in-house capacity.
You receive
Selected packages prepared under your brand, with a private review room and an explicit queue and SLA.
First safe step
Review a partner brand profile and the tiers you want to support.

If this path fits you confirm it in the guide →

Inside a delivery

What is actually inside a delivery.

Depending on scope, one reviewed project turns into coordinated documents, schedules and spatial files — each keeping a different part of the decision usable.

Illustrative deliverable anatomy — no client data

Illustrative page anatomy of a T1 Site Intelligence Brief
Inside a T1 Site Intelligence Brief — illustrative deliverable anatomy.

Illustrative deliverable anatomy — no client data

Illustrative two-book set of a T2 Landscape Concept package
The two books of a T2 Landscape Concept — illustrative deliverable anatomy.

PDF / XLSX / GPKG / CAD-GIS / visual set — only within the relevant scope.

  • PDF books carry the reviewed decision your team reads and shares.
  • XLSX schedules keep plant, water and quantity logic usable.
  • GeoPackage keeps the spatial evidence usable outside the PDF.
  • CAD-GIS exchange coordinates the landscape with architecture and consultants.
  • The visual set stays labelled as proposed, never as built.

See the full delivery anatomy →

Customer journey

One visible path — you always know the next step.

From the first file to the final delivery, each step shows what a client sees, without exposing the internal engine or any private data.

  1. Define

    This is the decision the site needs to support.

  2. Inputs

    Your upload is received — but not yet approved for technical use.

  3. Evidence & Design

    The read is being built; what is still missing stays visible.

  4. Review

    The correction reason is clear, and revisions stay traceable.

  5. Delivery

    Your approved, labelled package is ready.

Illustrative workflow for selected engagements

See the client workspace →

Accepted demonstration — no client data

Demonstration only — no client data Received

Files received safely.

The upload is attached to this demonstration project and will be reviewed before technical use.

Purpose
Concept-plan reference
Review state
Technical review required
Privacy
Demo data only
Demonstration only — no client data Action needed

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.

Human + system

Design authority and system authority are different responsibilities.

Two named responsibilities stay visible. The landscape decision is human; the system keeps that decision traceable from intake to delivery.

Zümra Timur

Landscape Architect & Design Lead

Interprets the brief, sets landscape and spatial direction, decides planting, material, water and visual language, reviews proposed visuals, and gives the named design QA.

One decision, end to end

  1. Raw evidence: shade pressure is high.
  2. Zümra decision: the arrival sequence needs canopy + layered planting.
  3. System control: the modeled claim remains distinct from measured geometry.
  4. Delivery: concept page + plant schedule + limitation note.

Tuncer Timur

Studio Systems Architect & Product/Evidence Lead

Owns the Studio OS and product architecture, safe intake and revision truth, the GIS, data and evidence infrastructure, the source, method and reproducibility limits, privacy, rights and white-label controls, and the review, package and delivery QA architecture.

AI can accelerate the process; the landscape decision and the release approval stay the responsibility of a named human.

Studio OS is not software sold to the client; it is the spine that keeps the work from getting lost.

Trust architecture

The evidence behind the product stays visible.

This is the proof that comes after the product, not before it. Public context is not a survey; a proposed visual is not a built result.

  1. Client-providedFiles and briefs arrive with a recorded origin and purpose.
  2. ScreenedSecurity, format and use checks run before anything is trusted.
  3. ModeledEvidence becomes landscape direction with a stated method.
  4. ReviewedA named human review is completed before delivery.
  5. ApprovedOnly approved work carries an approved label.
  • Known and unknown are both stated — never hidden.
  • Every figure carries its source, method, scale and date.
  • Revisions supersede; they never silently overwrite.
  • Rights and required attribution travel with the work.
  • A named human review is the release condition.
  • Nothing is auto-upgraded from modeled to measured.

Read the method →

Public context ≠ survey · Proposed ≠ built · Client approval ≠ public eligibility

Labels are not interchangeable.

Start here

Let's start from the question your project needs to answer.

Share the site, the files you already have and the decision point; we will choose the lightest safe scope together.

Discuss your project See the delivery anatomy