Automate the boring documentation. Keep the design.
Specsheets, schedules, cost estimates, revisions, reports. If your team retypes the same data into drawings, spreadsheets and slides on every project, we automate it — with software and AI built around the tools your studio already uses.
Our own lighting work: Larsen at De Doelen, Rotterdam
Today: typed into
Drawings Vectorworks · Revit · ArchiCAD
Spreadsheets Schedules · estimates
Presentations Studies · client decks
Supplier PDFs Datasheets · photometry
Email Questions · latest files
One source of truthProjects · products · revisionsEntered once, checked once
Generated, every time
Schedules From the model, every issue
Booklets & reports In your own layout
Cost estimates With working formulas
Client portal The latest approved files
Today the same information is typed into drawings, spreadsheets, presentations, supplier PDFs and email. With one source of truth it is entered once, and schedules, booklets, cost estimates and a client portal are generated from it.
Your discipline
Which studio are you?
Pick your discipline and jump straight to the examples that fit your work.
It's rarely the design. It's everything your team has to do to the design, again and again, on every project.
01
You type the same data three times
A product goes into your drawing, your schedule and your presentation by hand. One change means three edits, and one of them gets missed.
02
You collect product data by hand
Datasheets, photometric files and supplier pages, copied field by field into your own format.
03
Your schedules drift from the model
Quantities and schedules live next to the drawing instead of coming out of it, so every issue starts with a recount.
04
You reissue after every change
Revisions have to be tracked and documents reissued without losing what the contractor received last month.
05
You hunt for work you've done before
That detail, that fitting, that supplier from a project three years ago — somewhere in a dated folder.
06
You answer the same emails
Contractors and clients ask for the latest file, because the latest file lives in someone's inbox.
Before you build anything
What can you automate?
Think of one task in your studio and tick what's true. Frequent, repeatable work on digital information is where software pays back fastest — and we'll tell you what we'd do about it.
Score 0 of 9
Probably not worth software yetA rare or one-off task seldom pays back.What we'd do: We'll tell you honestly. Often a better checklist is all it needs.
A smart templateRepetitive enough that nobody should start from a blank page.What we'd do: We set up templates that fill themselves from your project data, so every document starts mostly done.
A script or small automationFrequent and rule-based: exactly what software is good at.What we'd do: We write the script, import or document generator around the tools you already use. Usually the quickest win.
A proper toolThis is where studios get days back on every project.What we'd do: We build you a private platform: one source of truth, every document generated from it, revisions kept.
How much could you save?
Your own numbers, for one repetitive task.
Hours back per year
184
Working weeks
4.6
Internal cost freed per year
€6,440
What fits
A proper tool
Weeks of your team's time every year. Worth one source of truth.
Counted over 46 working weeks and 40-hour weeks. This is your estimate of your own process, not a promise; the process review replaces it with a measured number.
How often × how long
Every task in your studio sits somewhere on this grid. Wherever yours lands, there's something we can do — except the bottom left, where we'll tell you to leave it.
Automate firstWe do this We build it for you: a platform or automation that takes it off your desk.
Script itWe do this We write a small script or connection, so it runs without anyone touching it.
Make a templateWe do this We set up a template that fills itself from your project data.
Leave it Not worth software. We'll say so.
Tick the questions above and your task's quadrant lights up.
Make a template
Automate first
Leave it
Script it
1Fixture or door schedule
2Cost estimate
3Revision reissue
4Product data entry
5Tender comparison
6Annual report
7Award entry
How often it happens →Time it takes each time →
Fixture or door schedule
Cost estimate
Revision reissue
Product data entry
Tender comparison
Annual report
Award entry
What we build
Four ways we can help your studio
Most studios need a mix. We start with the smallest thing that gives you back the most hours.
Automation
Scripts and connections between the tools you already have.
· Exports from Revit, Vectorworks or ArchiCAD into your templates
· Document generation in your layout: PDF, Excel, PowerPoint
· Dynamo, Grasshopper and Python scripts
· Hand-offs between apps with Make, n8n or Power Automate
Platforms
A private web app with one database, and every document generated from it.
· Product and fixture libraries you reuse across projects
· Revisions frozen per issue, with what changed
· Portals where your clients and contractors get the latest files
· Your visual identity, not a generic dashboard
AI
Reading, searching and drafting — with your designer checking the result.
· Fields extracted from datasheets and supplier pages
· Plain-language search across your past projects
· Meeting notes turned into actions per party
· EU-hosted models, or local models on your own server
Analysis
Dashboards and reports from your hours, budgets, models and sensors.
· Hours and budget per project and phase
· Quote comparisons item by item
· Light and climate data logged against limits
· Area and quantity checks against the brief
Use cases
Examples for your discipline
Real processes from design studios, and what software does with them. Pick your discipline; studio-wide examples apply to everyone.
Lighting Platforms
Fixture schedule and booklet from specsheets
Supplier PDFs become coded fixture records. Your schedule, fixture booklet and cost estimate are generated from them, in your layout.
Replaces · Copying specs from PDFs into CAD, Excel and slides
Vectorworks
Excel
PDF
LDT / IES
Lighting Automation
Photometric cross-check
A warning when the .LDT or .IES file disagrees with the datasheet on lumen, wattage or colour temperature.
Replaces · Spotting mismatches by eye, or not at all
LDT
IES
GLDF
Lighting AI
Luminaire search by specification
Find fittings across your past projects and manufacturer catalogues by beam angle, CRI, IP rating — or from a photo.
Replaces · Browsing catalogues and old schedules
Product library
Supplier catalogues
Lighting Automation
Calculation reports in one format
DIALux or Relux results collected into one consistent report per room or zone, ready for your client.
Replaces · Reformatting calculation output by hand
DIALux
Relux
PDF
Architecture Automation
Schedules straight from the model
Door, window and room schedules pulled from Revit or IFC into your Excel and PDF templates, refreshed on every issue.
Replaces · Recounting and retyping schedules
Revit
ArchiCAD
IFC
Dynamo
Excel
Architecture Analysis
Area statements, checked
Gross and net areas per floor and function, calculated from your model and compared with the brief before every submission.
Replaces · Manual area take-offs in spreadsheets
Revit
ArchiCAD
IFC
Excel
Architecture Platforms
Drawing issues and revisions
Every issued set frozen with its transmittal. See exactly what changed between revisions, sheet by sheet.
Replaces · Dated folders and transmittal spreadsheets
PDF
DWG
CSV
Architecture AI
Meeting notes to action lists
Notes or recordings turned into decisions and actions per party, filed with your project.
Replaces · Writing minutes after every meeting
Teams
Zoom
Email
Interiors AI
FF&E schedule from product links
Paste a supplier link and the name, dimensions, finish, lead time and price land in your schedule, with an image.
Replaces · Copying product details from websites
Excel
Airtable
Supplier sites
Interiors Analysis
Quote comparison
Supplier quotes read and lined up item by item, with differences in price and lead time highlighted.
Replaces · Side-by-side PDFs and a calculator
PDF
Excel
Exhibitions & museums Platforms
Object lists and label texts
Object data from your collection system flows into lists, labels and layout plans without retyping.
Replaces · Exporting, cleaning and pasting object data
Collection database
InDesign
Excel
Exhibitions & museums Analysis
Light exposure per object
Lux and UV logged per object against its yearly exposure budget, with an alert before a limit is reached.
Replaces · Spot measurements and estimates
Light sensors
Dashboard
Landscape & urban Automation
Plant and material schedules
Quantities from your drawing and species data from your library, combined into one schedule.
Replaces · Counting symbols and looking up species data
AutoCAD
Vectorworks
Excel
Landscape & urban Platforms
Asset and lighting inventories
Survey data, photos and condition per pole, tree or object on a map, exportable for the municipality.
Replaces · Spreadsheets and photo folders from site visits
GIS
CSV
Mobile forms
Studio-wide AI
Search across your past projects
Ask which project used a fitting, a detail or a supplier, and get answers that link to the source file. Can run entirely on your own server.
Replaces · Asking the colleague who remembers
Server folders
PDF
Email
Studio-wide Automation
Proposals and fee estimates
Fee proposals assembled from your scope templates and the hours of comparable past projects, in your layout.
Replaces · Starting every proposal from the last one
Excel
Word
InDesign
Studio-wide Analysis
Hours and budget per project
Time registration and budgets in one view per project and phase, so overruns show while there is still time to act.
Replaces · End-of-month surprises
Excel
Timesheet tools
Studio-wide Platforms
Client and contractor portal
One private page per project with the latest approved documents, so nobody works from an old zip file.
Replaces · Sending files by email and WeTransfer
PDF
DWG
IES
Studio-wide examples are shown with every discipline.
Your stack
Built around the software you already use
You don't have to replace anything. We connect through exports, file formats, APIs and scripts, so your drawing tool stays your drawing tool.
Design and BIM
Vectorworks
Revit
ArchiCAD
AutoCAD
Rhino + Grasshopper
SketchUp
Lighting
DIALux
Relux
AGi32
LDT (Eulumdat)
IES
GLDF
Office and data
Excel
Google Sheets
PowerPoint
InDesign
Airtable
Notion
Exchange formats
IFC
BCF
DWG
PDF
CSV
JSON
Automation
Python
Dynamo
Make
n8n
Power Automate
Zapier
AI
Mistral (EU)
Gemini on Vertex AI (EU region)
Claude
Local models via Ollama
Worked example
A fixture booklet for a lighting design studio
How we'd approach a platform for your studio, taken from a current proposal and shown without client details.
Before
Today the fixture booklet is built inside the drawing file, specs are pasted from supplier PDFs, and the same data is retyped into the cost estimate and the presentation.
1
Map one real project
One meeting at the studio, walking a recent project from specsheet to issued booklet.
2
Clickable prototype first
Every screen and the studio's own document layouts, clicked through before any code is written.
3
Specsheets in, fields out
A folder of PDFs becomes coded fixtures. AI fills the fields; a designer reviews each one, with the PDF alongside.
4
Every document generated
Booklet as PDF and cost estimate as Excel with working formulas, from the same record. Revisions are frozen per issue.
5
Confidential stays inside
Projects marked confidential are processed by a local model on the studio's own server.
After
The drawing tool keeps drawing and counting. Everything that is typed, checked or exported moves to one place.
Data and security
Your data stays yours
You work on confidential buildings and unreleased projects. The setup reflects that from the first line of code.
EU hosting
A dedicated server in the EU, or your own office server.
No training on your data
AI providers configured for zero retention and contractually barred from training on it.
Local AI when it matters
Confidential projects processed by open models on your own hardware. Nothing leaves your building.
You own it
Source code, data and documents are yours, with exports in CSV, Excel and JSON at any time.
Process
How we'd work with you
Nothing is built that you haven't seen first.
01
Process review
We sit with one of your real projects from start to finish and map where your hours go. You get a clear scope and price before anything is built.
02
Clickable prototype
Every screen and your document layouts, clicked through together and changed before any code is written.
03
Build in blocks
Short build blocks, each ending in a review where your own files go through the real thing.
04
Handover
Training, user and admin guides, the source code and your data. Small changes stay easy afterwards.
Typical timelines, in weeks
Process review1–4 weeks
A focused AI tool or automation4–12 weeks
A studio platform6–14 weeks
Typical ranges from our service pages, not commitments. The process review gives you the real number.
Background
Built by people who design and light things themselves
Hola Studio started by designing and manufacturing lamps, and still lights concerts and theatre. Fixture codes, photometric files and renvooi tables are familiar ground — we speak your language.
Clients includeMuseum Boijmans Van Beuningen · Municipality of The Hague · The Hague University of Applied Sciences
FAQ
Questions you might have
Do we have to stop using Vectorworks, Revit or Excel?
No. Your drawing and BIM tools keep doing what they're good at. We connect to them through exports, file formats, APIs and scripts, and move only the typing, checking and document work.
Is our project data used to train AI models?
No. We use EU-hosted AI with zero retention and no training on your data, and for confidential projects the AI can run entirely on your own server.
Can it run on our own server?
Yes. A platform can be hosted on a dedicated EU server in your name, or on the server already in your office, with local AI models for confidential work.
We're a small studio. Is it worth it?
Often the first win is small: one script or one generated document that saves you a day per project. Use the check on this page; if a task is frequent, repeatable and already digital, it's usually worth a conversation.
What does it cost?
We don't publish prices, because scope decides it. The process review maps one of your real projects and ends with a clear scope and price before anything is built.
How long does it take?
Typically 1–4 weeks for a process review, 4–12 weeks for a focused AI tool or automation, and 6–14 weeks for a studio platform.
Who owns the software?
You do. You receive the source code, the data and the infrastructure accounts, with no lock-in.
Do you work outside the Netherlands?
Yes. Hola Studio is based in Rotterdam and works with studios internationally, in English or Dutch.
Bring one project. We'll show you where your hours go.
Tell us how a project moves through your studio today. We'll tell you honestly what's worth automating, and what isn't.
Hola — I'm Ola. I know how the studio works: what we build, how we scope
it, and what engagements usually cost.
Ask me anything, or tell me what you're trying to make.
A quick, honest question
We would like to use Google Analytics to see which work people actually
read. It sets cookies and shares your visit with Google, so we are not
turning it on unless you say yes. The site behaves identically either
way. What we collect.