AI.Architect
Proposal
01 / 15
Proposal for an architecture studio · Tbilisi

AI Architecta working version in 8 weeks

An internal studio tool: the lead architect provides a sketch and requirements, then receives a checked scheme and structured data for local work in Revit.

8 weeks
fixed delivery cycle
$15,000
development budget
1 workflow
captured and transferred into the system
3–5 projects
validated on the studio’s own work
01 Business challenge

The studio’s main constraint is team throughput

Your time should go into decisions. Today, part of it is spent briefing and rechecking work.

Sketches, explanations, regulations, budget limits and dozens of revisions pass through junior architects before returning to you for another review.

The first version keeps you in control while reducing the repeatable work between a decision and its verification.

Decisions
remain with the lead architect
Routine
areas, drafting and repeated revisions
Tool
handles the agreed part of the work
Growth
more projects without proportional headcount
02 Studio owner’s goal

First the tool improves the studio’s productivity; then it becomes a standalone product

The lead architect remains the author and makes the decisions. Repeatable operations gradually move into one working system.

Start here

Design

A sketch and brief become a scheme, area schedule, agreed revisions and a structure file for Revit.

Next layer

Review

The set of regulations, internal standards, sources and reproducible checks expands over time.

After demand is validated

Client intake

The website questions the client, collects source information and prepares the design brief.

Commercial stage

SaaS for studios

A process proven internally becomes a service that can be sold to other architects.

The order of later modules depends on measured time savings and the constraints found in the studio’s real projects. The next scope is set after the first version is evaluated.
03 First iteration

The first iteration removes one specific workload from private-house design

Initial candidate: a private house, taking the lead architect’s sketch through schematic planning and checks to structured data for a local Revit plugin.

Input 01
Sketch
Image or PDF with notes
Input 02
Brief
Site, rooms, areas and constraints
Processing
Digital scheme
Rooms, walls, relationships and parameters
Review
8–12 rules
Calculation, source and clear variance
Output
Plan + structure
Scheme, report and file for the Revit plugin
The exact building type and output format are agreed in week one using real studio materials.
04 What will work by the end of week eight

You take a project yourself from brief to Revit-ready structure

“Digitise this sketch. Keep the total area unchanged. Enlarge the living room, move the kitchen closer to the terrace and check the agreed site constraints.”

The architect receives a measurable structure that can be reviewed and changed.

01

The brief is captured without omissions

Requirements are stored as fields; missing inputs are shown separately.

02

Scheme + structure file

The file is exported manually; the installed plugin reads it and creates the agreed elements in the local Revit template.

03

Checks with a clear reason

Every rule shows its calculation, source and variance.

04

Revisions without rebuilding

Room area, position or relationships change within the current project version.

05 Example output

What you open after one pass

An illustrative private-house scenario. The exact output is agreed on the studio’s own projects in week one.

You provide

A sketch and design brief

  • 30 × 40 m site
  • Two floors, approximately 450 m²
  • Room schedule and target areas
  • Local Revit with the plugin installed
Private house · option 03
Ground floor · 228 m² · updated after revision
ready for review
Living room54.8 m²
Kitchen–dining41.2 m² · terrace access
Hall23.4 m²
Study15.6 m²
Guest room18.1 m²
WC6.2 m²
Latest revisionLiving room enlarged to 55 m². Kitchen moved closer to the terrace. Total area retained.
Areawithin tolerance
Setbackspassed
Intersectionsnone found
You receive

Working materials

  • Schematic plan in PDF
  • Room and area schedule
  • Log of agreed checks
  • Structure file for manual import
  • After import to Revit: levels, walls, rooms, doors and windows
  • Brief and revision history
This mock-up shows the composition and structure of the output. The interface design will be refined during the work.
06 Scope of the first investment

The first investment buys a complete working loop

$15K includes

  • One agreed project type and one workflow
  • Internal web interface and storage of a lightweight project structure
  • Sketch, written brief and structured parameters
  • Schematic 2D geometry and area schedule
  • 8–12 formalised rules and a check log
  • Several pre-agreed revision types in dialogue
  • Manual export of the structure from the website and a local Revit plugin that reads it
  • One template and an agreed set of generated elements

Outside this iteration

  • Complete construction or permit documentation
  • A complete library of Georgian building regulations
  • Structural calculations and engineering disciplines
  • Storage of complete .rvt projects or one-click opening
  • Autonomous design without an architect
  • Reliable recognition of any free-form sketch
  • Full BIM exchange, families of any complexity and model coordination
  • Public SaaS, billing and sales automation
07 How the output reaches Revit

Large Revit files stay on the studio’s computers

01 · Website

Lightweight project structure

Floors, rooms, walls, areas, relationships, rules and versions. A complete .rvt file is not stored online.

structure / versions / checks
02 · Architect’s action

Manual export

The architect downloads the structure file and selects it in the installed plugin.

website → structure file
03 · Workstation

Local Revit plugin

The plugin is installed separately, reads the structure and creates agreed elements in the local template.

file → levels / walls / rooms
A complete Revit project is not downloaded from the website. The structure format, Revit version and generated element set are agreed in week one. Reading and creating elements has already been validated with the Revit Add-in prototype; API reference: help.autodesk.com/cloudhelp/2026/ENU/Revit-API/
08 Georgian regulations

Version one includes only rules with a deterministic answer

Footprint within the buildable areageometric check
Setback no less than Xformula + source
Total area within tolerancecalculated from model
Required room is presentstructural check
Minimum area/widthfor the selected type
No obvious intersectionsgeometric check
The final decision remains yours

Every rule shows its source, version and result

The system does not provide a legal guarantee of compliance. The studio first defines each rule precisely; it is then implemented and tested against known examples.

Georgia’s Code regulates land use, building requirements and permit procedures; the effective text was amended in 2026. Source: matsne.gov.ge/en/document/view/4276845. Rules must therefore be versioned and confirmed by a qualified specialist.
09 Eight weeks

Every two weeks you receive a part you can open and verify

Weeks 1–2

Define one workflow

  • 3–5 real projects
  • exact inputs and outputs
  • site and building structure
  • 8–12 rules
Outcome: a formal test set and acceptance specification.
Weeks 3–4

Build the working core

  • web project
  • brief and parameters
  • lightweight building structure
  • visualisation and areas
Outcome: the first project moves from input to a digital scheme.
Weeks 5–6

Add revisions and the Revit plugin

  • change commands
  • formal checks
  • structure-file export
  • local import to Revit
Outcome: you manually transfer the website structure into local Revit.
Weeks 7–8

Test in practice

  • remaining projects
  • edge cases
  • fixes and stability
  • deployment and handover
Outcome: the studio runs a demonstration project independently.
10 How you accept the result

Acceptance is based on 3–5 studio projects

3–5 projects complete the full workflow

We test with anonymised real materials from the studio.

The result is structured

Rooms, walls, relationships and areas are available to the system as data.

Revisions apply to the current version

Agreed changes are made to the project and checked again.

Every check is reproducible

The same input produces the same calculation, rule source and clear variance.

You can work without a developer

Create a project, export its structure and import it manually with the installed Revit plugin.

The next step’s return is measurable

We measure time to result, manual revision volume and reasons for failed runs.

11 What both sides contribute

Your involvement is needed where lead-architect judgement matters

You and the studio define the professional standard

  • You make the key decisions on project type and output quality
  • Provide 3–5 completed projects: inputs, intermediate materials and final result
  • Define what counts as a good or unacceptable solution
  • Provide the Revit version, template and workstation for plugin installation
  • Join a 60–90 minute weekly review

Our team turns that standard into a tool

  • Define boundaries and acceptance criteria
  • Build the web interface and lightweight structure storage
  • Build the digital building model and geometric calculations
  • Implement the export format and local Revit plugin
  • Deploy, document and hand over the working version
12 Cost of the first iteration

A complete working loop costs $15,000

Problem definition and test set$2,000
Structured model + rule package$3,000
Web interface and structure storage$2,000
Dialogue and agreed revision scenarios$3,500
2D, export format and Revit plugin$2,500
Pilot, stabilisation and handover$2,000
Total$15,000

The budget is kept within range by focusing on one project type and using the already validated Revit workflow. Hosting, paid models, Autodesk and other third-party licences are paid separately at cost.

$15K
fixed budget for one eight-week iteration
$5Kstart and team reservation
$5Kworking-core demo · week 4
$5Kpilot, deployment and handover
13 After the first version

The next iteration is chosen from actual time savings

At the end of week eight you have three figures: time to result, volume of manual revisions and the share of projects completed successfully.

Path A

Deeper architectural design

More revision types, options, floors, stairs and spatial constraints.

If the bottleneck is planning quality and flexibility.
Path B

Deeper BIM

More categories and families, data exchange back to the website, sheets, schedules and coordination.

If manual import proves its value and becomes the next bottleneck.
Path C

Client intake

Website dialogue, lead qualification, source-data collection and brief preparation.

If handling new enquiries limits growth more than production does.
Path D

Commercial SaaS

Users, roles, data isolation, billing, audit and an interface for other studios.

Only after the internal value is proven in your studio.
14 Proposed start

In eight weeks the studio gains another working tool

You remain the project author and decision-maker. The website creates the structure; after manual export, the locally installed plugin transfers it into Revit.

This proposal is preliminary. Exact input formats, rules, code ownership, data location and support terms will be defined in the contract and technical appendix.