Built by an architect who knows
what this work costs you.
Ofivio is the workspace we wished existed on the hard days — the night before a submission, the month payroll was tight, the drawing nobody could find when the client asked. It wasn't dreamed up in a boardroom. It was built inside a working studio, by someone living the same week you're living.
It started with a bad month, not a business plan
Ofivio didn't begin as an idea. It began as exhaustion. Running a design practice in Lahore meant holding a whole studio together across AutoCAD folders, 4,000-row Excel BOQs, a Tally file for accounts, a wall of WhatsApp groups from site, and a shared drive full of files named Final_v3_FINAL. None of it talked to each other. On Monday morning we couldn't honestly say whether the work of the previous week had left us better off or worse — and there were people depending on that answer.
We tried the tools everyone recommends. Every one of them was written for software teams or generic offices, and every one of them asked us to pretend our work was something it isn't. No drawing revisions. No bill of quantities. No transmittal log. No difference between a design fee and a supervision fee. Using them felt like being told the way we work is the thing that's wrong.
It isn't. So we stopped searching and started building — quietly, for our own studio, one painful problem at a time. It kept working. Other practices started asking for it. What began as a way to get our own evenings back was rebuilt from the ground up and became Ofivio: one connected workspace that follows the way an a practice actually thinks — drawings → revisions → phases → BOQ → procurement → site → handover. Same data, same login, and every person on your team sees exactly what they need and nothing that isn't theirs.
"I don't know your practice. But I think I know your Tuesday."
It's late. The submission is tomorrow. Someone has sent the wrong revision to the client and you won't find out until Thursday. There's a payment that was promised last month and still hasn't come, and you already know that if it doesn't arrive by the 30th, you'll quietly cover salaries yourself and tell nobody. Your team will go home tonight believing everything is fine. That belief is something you carry alone.
I know that week because I've lived it. I'm an architect — tracing paper, AutoCAD, dusty sites in Lahore, contractors who argue, clients who mean well and pay late. For years I believed the mess was my failing. That a better-organised person would have this handled. I want to say this plainly to anyone who needs to hear it: it was never you. The work is genuinely this complicated, and you have been doing it without a single tool that respects how it actually happens.
That's what hurt the most, honestly. Not the long hours — architects choose those. It was watching good people burn out on the parts of this profession that have nothing to do with architecture. A brilliant young designer spending her evening renaming files. A site engineer photographing work that nobody will ever open again. A principal who hasn't drawn anything in two years because someone has to chase the invoices.
So I built the thing I needed. Not to disrupt an industry — I have no interest in that word. Just to give a few hours back to people who are already giving everything they have. I built most of it myself, at night, with AI as a co-pilot instead of a hundred engineers. It's not perfect. I'm still fixing it. But every part of it exists because it cost someone something first.
If Ofivio means you make it to dinner, or sleep through one night you'd otherwise have spent doing sums, or look at a screen on Monday morning and simply know where your practice stands — then it has done its job. That's the whole ambition. It's enough.
And if you ever want to tell me what's still broken, write to me. Not to a support queue — to me. I read them all, and I answer.
Four promises, in plain language
You've been let down by software before. Fair enough. So here is what we owe you, written the way we'd want it written for us.
A person answers you
Not a ticket number, not a chatbot loop. When you write in, an architect who has had your bad week reads it and replies.
Your work stays yours
Your drawings, your clients, your numbers. Isolated from every other practice on the platform, never sold, never mined, and yours to export the day you choose to leave.
We won't waste your time
No forced migrations, no redesigns that move everything you already learned, no feature you have to relearn on a deadline week.
Solo practitioners are never priced out
If you're starting alone, the core of Ofivio is free and stays free. We remember what year one felt like.
Five disconnected tools, and one person holding them together.
Drawings live in CAD folders. BOQs live in 4,000-row Excel sheets. Site updates live in WhatsApp groups. Invoices live in Tally. Payroll lives somewhere else entirely. The only thing joining them is a human being who never gets to switch off.
So on Monday morning nobody can say whether last week made money, who is drowning, who is idle, or which drawing the client actually signed. Not because anyone was careless — because no tool ever made it possible to know.
One workspace — and your evenings.
Drawings, revisions, BOQ, procurement, site supervision, client approvals, fees, payroll, and VO — the built-in AI assistant that speaks English and Urdu — all connected, so the answer is already there when you need it.
Shaped around the way project work actually runs, so nobody on your team has to bend themselves to fit software again.
From an internal fix to a platform
One studio, too many tools, not enough hours
A practising architecture studio in Lahore, held together by Excel, WhatsApp, Tally and CAD folders that never spoke to each other — and by people staying far too late. The first sketches of a better system were drawn out of tiredness, not ambition.
An internal system takes shape
The earliest version — then called Vevarte — was a small in-house tool to track projects, BOQs and site progress. It worked. It kept growing. It started solving problems other firms had too.
Rebuilt from the ground up as Ofivio
Re-architected for real multi-studio use: hard tenant isolation, thirteen roles, a native dual-BOQ engine, phase-aware fees, and an AI assistant. Ofivio became a product, not just a workaround.
One login, twelve connected platforms
Ofivio is live in production — 283+ pages, 214+ APIs, a voice-capable AI assistant, mobile apps, and a wider Ofiverse of connected platforms around the core studio OS.
From solo practitioners to multi-office studios
Design practices
Architecture, interiors and engineering — solo to multi-office
Interior studios
Residential, commercial, hospitality
Design-build contractors
Design + execution under one roof
Construction consultants
PM and supervision firms
Quantity surveyors
BOQ and cost-control specialists
MEP consultants
Mechanical, electrical, plumbing offices
Structural offices
Coordination with the design team
In-house design teams
Real-estate and developer studios
Built for the work, not adapted to it
Phase-aware everything
Concept → Schematic → DD → CD → Execution → Handover. Fees, deliverables, and team time tracked per phase.
Native BOQ with volume groups
Rate library, engineer's estimate vs proposed BOQ, live P&L, one-click BOQ-to-PO conversion.
Mobile-first site supervision
Daily reports, photos, snag list, labour and material logs — built for filling on a phone, on a dusty site, with patchy 3G.
Real client approval flow
Send drawings for sign-off, client approves or objects with comments, immutable audit trail. No more 'didn't see your email.'
Dual-fee model
Design practices run on two fee streams — design and supervision. Tracked, invoiced, and reported separately.
Drawing transmittal log
Drawing sets with revision history, who issued what to whom, which version is current, what's superseded.
Don't take a picture's word for it
Most software asks you to sign up before it shows you anything. Pick half an hour and somebody who builds Ofivio will walk one of YOUR projects through it — the ledger, a priced BOQ with its real margin, the roster. No account, no card, and if it does not fit your practice we will say so on the call.
Three things we refuse to get wrong
Your studio, sealed
Your fees, your clients, your drawings — kept physically separate from every other practice on the platform, enforced at the database layer rather than trusted to application code. Your competitor down the road will never see a single row of it.
Nobody waits for news
Drawings, comments, approvals and site updates appear the moment they happen — on the team's dashboards, in the client portal, on your phone at the site gate. The person who needs to know already knows.
Dignity by design
Thirteen roles, each shown what belongs to them. The intern isn't exposed to partner-level fees, the site engineer isn't handed your margins, the client sees their own project. Privacy inside a team is a kindness, not a lock.
Beyond the practice — connected platforms
Ofivio is the studio. Once your practice runs on it, a family of connected platforms extends it — an internal social feed, a blog to publish your work, a professional network for the industry, a marketplace for CAD blocks and finishes, a portfolio site auto-built from your project archive, and a learning hub. One sign-up, one subscription, all of them.
How it's built
Stack
React + TypeScript frontend, Express + Node.js backend, Firestore database with hard tenant isolation. Hosted on Google Cloud Platform across thirteen Firebase sites with global CDN and automatic SSL. Mobile via Capacitor on Android (iOS in review).
AI
VO assistant — a command centre spanning projects, BOQ, finance, HR and reporting. Speaks English and Urdu, works by voice, and is tuned with its own personality and memory per studio.
Pricing
11 products, priced by team size. Your bill is the product, plus any whole dashboards you add, plus VO per seat — and it stops at a ceiling that unlocks everything. Billing is in USD, shown in your local currency, and settled by EasyPaisa, JazzCash or bank transfer.
Built in Pakistan
Designed and built in Lahore, hosted globally for low latency. Pricing, language, payment rails, and feature priorities are tuned to how project businesses actually run here — and ready for the rest of the world.