01//
Product thinking
Start with the problem, users and workflow. Build the right thing before optimizing the wrong thing.
Taking on selected projectsSerbia / WorldwideDesign / Engineering / Production
Digital product studio
BUILDWHATMATTERS.
CMake Studio is a Serbia-based web development and software studio turning ideas and business problems into complete digital products — interface, application logic, integrations and production kept in one build.
WEBSites + applications
SOFTWARETools + automation
SYSTEMSAPIs + infrastructure
CMake Studio / Digital productsSerbia / Worldwide
DesigninterfacesBuildsoftwareConnectsystemsShipproduction
How the build moves
One loop from rough idea to production.
The process stays direct: understand the real problem, shape the right product, engineer it, then put it where it has to work.
No handoff maze between strategy, interface and implementation. The same context follows the project through the build.
cmake / product.build
Ready for the next build
$ cmake --project your-idea --target production
FULLstack
1→1direct
SHIPfocused
01Why CMake
One studio across the whole build.
The advantage is not simply writing code. It is keeping the product, interface, application logic, integrations and production environment connected from the beginning.
02//
Design + frontend
Clear interfaces, responsive behavior and a visual system that feels intentional on every screen.
03//
Backend + APIs
Business logic, databases, dashboards and integrations built as part of the product — not an afterthought.
04//
Production systems
Deployment, Linux, Docker, domains and the technical environment the product needs to run reliably.
02Selected work
The strongest proof is the product itself.
Each case study focuses on the actual system: what had to work, what was built and how the interface, logic and operations fit together.
01 / CASE STUDYFull web system + dashboard
AutoDelovi
A complete operational web system with its own dashboard and two connected custom APIs — built as a real business product rather than a brochure website.
Full web systemDashboardBackendAPI development
Open case study →02 / CASE STUDYOrdering platform
Foto Zrak
A photography and print-ordering experience that turns uploads, sizes and production requirements into a clear customer workflow.
Product designFrontendAdmin dashboard
Open case study →03 / CASE STUDYMedical interface
ALVI Dashboard
A modular clinical dashboard focused on surfacing patient information quickly without turning complex data into visual noise.
UI systemDashboard designFrontend
Open case study →04 / CASE STUDYInfrastructure + automation
Custom Systems
Purpose-built internal tools, servers and automation for workflows that do not fit inside off-the-shelf software.
AutomationLinuxInfrastructureInternal tools
Open case study →03 / Flagship system
A website can become the software that runs the work.
AutoDelovi is the clearest example: customer-facing product, operational dashboard, backend logic and custom APIs treated as one connected system.
Core platformFull web system
Customer experience, backend logic and workflow in one product.
OperationsLive dashboard
A dedicated control surface for the people operating the system.
Connectivity2 custom APIs
Purpose-built integrations connecting external services to the platform.
04Connected build
A product is more than the screen people see.
Interface, logic, data, integrations, automation and production all influence each other. Keeping those layers connected produces better decisions and fewer surprises.
Connected capability
The browser is only one layer.
Good products are shaped by what happens across the whole system. CMake Studio keeps interface, logic, data and production decisions connected.
01 / Interfacesystem layer
Clear product UX and responsive interfaces built around the people using the system.
05Services
Choose the outcome. The stack follows.
Starting prices give useful context. Final proposals are based on scope, complexity, integrations and the responsibility the product carries.
01From €1,200
Business websites
Credibility, positioning, performance and conversion.
Explore →02From €3,500
Web systems + dashboards
Dashboards, portals and operational products.
Explore →03From €2,500
Custom software
Purpose-built tools for real workflows.
Explore →04From €400
APIs + integrations
Connect services and move data reliably.
Explore →05From €1,500
AI + automation
Remove repetitive work with useful automation.
Explore →06From €750
Infrastructure + deployment
Deployment, Linux, Docker and production systems.
Explore →06Project planner
What are you trying to build?
Choose the closest starting point to see the typical entry level and what that kind of engagement can include. It is guidance, not an instant quote.
From €3,500
Web systems + dashboards
Full web applications, dashboards, portals, ordering systems, booking tools, SaaS products and custom operational platforms.
Discuss this project →Final proposal depends on scope, complexity and integrations.
Typical engagement02
01Product UX
02Frontend + backend
03Dashboard / admin
04Database + deployment
07Process
A clear path from conversation to production.
Enough structure to keep scope and responsibility clear, without burying the project in ceremony.
01
Understand
Define the business problem, who uses the product and what should become easier or more valuable.
02
Architect
Shape the scope, interface, data and technical path before complexity spreads through the build.
03
Build
Design and engineering move together with working progress you can review as the product takes shape.
04
Ship
Test, deploy, connect the domain and put the product into the environment where it has to work.
05
Evolve
Continue with features, maintenance, optimization or infrastructure as the product and business grow.
01
Clear scope
Know what is being built and why.
02
Working progress
Review the product as it takes shape.
03
Production path
Deployment is considered during the build.
04
Clean handoff
Access and responsibilities are explicit.
08Insights
Useful thinking before a project becomes code.
Practical notes on web architecture, custom systems and integration engineering — written from the decisions that matter during real builds.
017 min read
Product decisions / Web architecture
Website or web application? Choose based on the job, not the label.
Read insight →029 min read
Custom software / Product architecture
How to plan a custom business system before writing code.
Read insight →038 min read
APIs / Integration engineering
API integration checklist: what makes a connection production-ready?
Read insight →09Questions
Enough detail to know if we fit.
01Do I need a finished specification?+
No. A rough idea, problem or workflow is enough to start. The first part of the process is turning that into a clear scope and technical direction.
02Can you handle both design and development?+
Yes. The goal is to keep product thinking, interface design and engineering connected instead of handing the work between disconnected teams.
03Do you work on existing projects?+
Yes. Existing sites, applications and systems can be audited, repaired, extended, redesigned or integrated with new services.
04How is pricing decided?+
The listed prices are starting points. A proposal is based on scope, complexity, integrations, risk and the amount of custom product work required.
05Can you deploy and maintain what you build?+
Yes. Deployment, Linux/server work, Docker, monitoring and ongoing maintenance can be included when the project needs them.
06Can the first version start small and expand later?+
Yes. When that fits the product, the first release can focus on the highest-value workflow while the architecture leaves a sensible path for later features.
07What happens with source code and handoff?+
Ownership, source access, hosting and handoff are defined clearly in the proposal for the specific project so there is no ambiguity about what is included.
08Do you work outside Serbia?+
Yes. CMake Studio is based in Serbia and can work remotely with clients internationally.
From idea to production.
Bring the problem. Build the right system.
You do not need a technical brief. Start with the problem, the goal and enough context for a useful conversation.