Build it, show it, sell it — off one set of records.
Five products for developers and contractors working in Bulgaria. Arcon runs what happens on site. The visual layer sells the building long before it exists. Both read the same units, so the availability a buyer sees is the availability you actually have.
Arcon ERPUnreal Engine 5Plovdiv · working across Europe
5products, one data model
EUhosting and e-signing
5languages out of the box
02
Why this exists
Construction runs on one set of tools. Sales runs on another.
A developer's site paperwork lives in folders and group chats. The sales pipeline lives in a spreadsheet. The website's availability table was last edited by hand three weeks ago. Nothing is wrong with any one of them — the problem is that none of them agree, and the disagreement usually surfaces in front of a buyer.
Availability that lies
A unit is reserved on Monday and still shows free on the website on Friday. The sales team finds out from the buyer.
Proof kept as paper
Certificates, inspections and deliveries end up as photos in a chat. When somebody asks who approved what, the answer takes a week.
Renders that age out
Visuals get commissioned per campaign, so every price change or layout revision means paying an agency to redo them.
Costs found out late
The real cost of a floor is known once the invoices are in — long after the decision that set it was made.
03
The platform
One record underneath, many surfaces on top.
Everything we build sits in three layers. The bottom layer is the record of what is true on site. The middle layer turns that into something a buyer can walk through. The top layer is where they find it. Each layer is useful on its own, and each one gets better when the layer under it is in place.
Layer 03 · Surface
Your website
Where a buyer meets both — live availability, real prices, and an enquiry that lands back in Arcon.
Layer 02 · Visual
Configurator, interiors, film
The building rendered so it can be explored: city scale down to a single room, plus the footage a campaign runs on.
Layer 01 · Record
Arcon ERP
What was delivered, inspected, signed and sold — with an author, a timestamp and proof attached to each.
You do not have to buy the whole stack. Most clients start with one layer and add the next once it has paid for itself.
04
Product 01 · Foundation
Arcon ERP — the system of truth for the site.
Everything in Arcon is a record: a delivery, an inspection, an incident, a request, a certificate. Each carries an author, a timestamp, a state and its proof. The modules work on top of those records rather than beside them, which is what makes the audit trail a by-product of ordinary work instead of a separate reporting exercise.
Approvals as data
Certificates and inspections are structured records that can be queried and chained, not scans in a folder.
Gated by condition
A permit can require a photo, a weather window, a specific role, or a prior certificate before it opens.
Priced on your terms
No price catalogue. You enter real invoices, and the bill of quantities is priced from what you actually paid.
Works offline, on site
Records are captured where the work happens, including where there is no signal, and sync when there is.
Built to Bulgarian practice
The data model starts from Bulgarian construction law and tax reporting rather than adapting a generic ERP: Act 12/14/15/16/19 certificates, ДНСК and РИОСВ requirements, qualified e-signing through eIDAS providers such as Evrotrust and B-Trust, counterparty lookup by EIK, and the SAF-T standard the platform is being built toward.
The 3D configurator — sell the building before it exists.
A city-scale scene rendered in Unreal Engine 5 and streamed to the browser, so a buyer explores the development at full quality without installing anything. They pick a building, then a floor, then a unit, and see its real orientation, its real view, and whether it is still free.
City scale to single unit
One continuous scene: the masterplan, a block, a floor plate, and the apartment itself.
Real sun and real views
Light is simulated by date and hour, and the view out of a window is the view that unit will actually have.
Availability from Arcon
Sold, reserved and free are read from the record, so the model cannot drift away from the truth.
Runs in a browser
Streamed from a GPU server. No app, no download, and the same experience on a laptop or a phone.
Photorealistic interiors for the units a campaign is built around — the show apartment, the penthouse, the common areas. Delivered as stills for print and social, as 360° panoramas that drop into the configurator, and as a walkthrough where the unit justifies one.
Interior renders from a delivered project — the same scenes feed the configurator, the website and the print campaign.
Concept to final frame
Mood board, palette, materials and furniture specified per room, then rendered.
Every output format
Print-ready stills, social crops, and panoramas that go straight into the 3D.
Reusable, not per-campaign
The scene stays live, so a revised layout or finish is a re-render rather than a new commission.
07
Product 04 · Visual
Drone and ad production.
The footage a launch runs on: 4K aerials that place the development in its actual surroundings, ground-level cinematography of what is already built, and edits cut for each platform the campaign lands on.
Aerial and ground
Scouted, scripted and shot — multiple altitudes and angles, plus interiors and common areas.
Cut for each platform
A hero film, vertical social cuts and standalone stills, subtitled for the markets you sell into.
Cut against the 3D
Real footage and rendered footage in one edit, so phases that do not exist yet sit beside the ones that do.
08
Product 05 · Surface
The website the whole thing lands on.
A marketing site built for one development, or for the company behind several. The configurator is embedded rather than linked, availability is live, and every enquiry arrives as a record in Arcon with the unit it came from attached.
Configurator embedded
The 3D sits inside the page, not behind a button on someone else's domain.
Live availability
Prices and unit status come from the record, so nobody edits an availability table by hand.
Leads with context
An enquiry carries the unit, the floor, and what the buyer looked at before sending it.
Five languages, fast
EN, DE, BG, TR and RU, built to load quickly for buyers browsing from abroad.
The products are worth having on their own. What makes them a platform is that a single unit is the same object in all of them — so a change made once shows up everywhere it should, and nowhere it should not.
01
It exists in Arcon
The unit is a record: floor, layout, area, orientation, and the certificates that accumulate against it as it is built.
02
It gets a body
The configurator renders it in place — its real floor, its real aspect, the actual view from its windows.
03
It gets dressed
Interior renders and panoramas attach to it, and the drone footage places the building it sits in.
04
It goes on sale
The website shows it as free, with a price from the record and a 3D view the buyer can walk.
05
It comes back
An enquiry, then a reservation, lands on the same record — and the configurator and the website stop offering it, in the same minute.
That last step is the point. Marking a unit reserved is one action, not four, and there is no window in which the website is still selling something the sales team has already taken off the table.
10
Where to start
You do not have to buy all of it.
Each product stands on its own, and each entry point leads somewhere sensible. These are the three we see most often.
01
Start with the site
For contractors whose problem is proof and cost control. Arcon first; the sales layer comes when a project reaches market.
02
Start with the launch
For a development going on sale soon. Configurator, interiors and film on a website — with Arcon added once the pipeline outgrows a spreadsheet.
03
Start with the website
For developers whose current site is the bottleneck. A fast multilingual site now, with room to embed the 3D and connect Arcon later.
Whichever way in, nothing is thrown away later — the pieces are built to connect, not to be replaced.
Next step
Tell us what you are building. We will map it to the stack.
A short call is usually enough to work out which layer is worth starting with, and what it would take.
