2024
ARCHKIRS.SITE
Public website + internal business system
Case study by Ian Kirs · ARCHKIRS
- Web Development
- Automation

About the project
ARCHKIRS.SITE started as a personal architecture portfolio and gradually became a connected digital system: the public multilingual website works together with Project Estimator and a protected internal workspace for commercial operations.
The public side presents architecture and Web & AI projects, services, and enquiry flows in Russian, Serbian, and English. The internal side supports clients and projects, proposals, contracts, payment stages, and documents without moving data between disconnected tools.
Public and internal areas are separated. Private rates, commercial calibration, and internal operational data are not exposed through the public interface.
Challenge
Connect the public website and internal commercial workflow in one system without turning the website into a public admin panel or duplicating clients, projects, and documents across disconnected services.
Solution
The public and protected areas are built as separate layers of one product. Public Estimator sends a structured request into the internal workflow, which then continues on canonical client and project records. Commercial calculations, document versions, and private data remain server-side and inside the protected owner interface.
What was implemented
- 01
Multilingual RU / SR / EN public website with architecture portfolio, Web & AI case studies, services, SEO, and structured JSON content.
- 02
Project Estimator that stores a structured enquiry and carries it into the internal workflow.
- 03
Billing Core with clients, projects, payment stages, multicurrency documents, and official NBS exchange rates.
- 04
Managed B2B contract preparation with immutable versions, multilingual packages, PDF output, and protected client review.
- 05
Precise Proposal calculator for supported scenarios: private versioned Price Book, deterministic calculation, controlled owner adjustment, and immutable RU / SR / EN proposals with PDF archive.
- 06
Separation of public and internal data: private rates, secrets, and internal logic are not sent to the browser.
Gallery
Business value
- One connected path from the first enquiry to commercial project preparation instead of disconnected spreadsheets and services.
- Client and project remain canonical records, reducing repeated data transfer between Estimator, Billing, Proposal, and contract workflows.
- Versioning and immutable documents make it clear which proposal or contract version was reviewed and used.
- The architecture allows new internal workflows to be added gradually without cluttering the public website or exposing private commercial information.
What this system deliberately does not do
- The public website does not expose private rates, commercial calibration, secrets, or internal operational data.
- Public Estimator does not turn the browser into the commercial calculation layer: protected pricing logic and documents remain server-side and inside the internal workspace.
- Internal tools do not make commercial decisions for the owner: proposal adjustments, contract versions, and final approval remain controlled owner actions.
Related guides
Technologies
Next.js · React · TypeScript · Tailwind CSS · Supabase · OpenAI
Need a similar system?
If you need more than a website - a connected work tool, client portal, or automation for a specific process - tell me about the task. We can start with a focused part and expand the system gradually.