A website as a working tool, not a one-off project
The difference between a site that lasts a month and one that lasts years is in the foundation: content structure, access rights, languages and the ability to add a section without a developer.
01Brief and estimateWe review the task, size the work and put the scope in writing — before the start
02StructureSections, page types and visitor journeys — before the first screen is drawn
03DesignKey pages at three sizes, with your own copy and photos
04DevelopmentFront-end, admin panel and forms; visible on a staging address from week one
05Content and checksContent is migrated; speed, forms, languages and phone behaviour are verified
06Launch and supportMigration with redirects from the old URLs, team training and watch after launch
PROJECT STAGES
How a project runs from brief to support
project.vmtech.rs
Project: corporate website
OK
Brief and estimate
estimate
Structure
sitemap
Design
mockups
Development
staging
Content and checks
ready to launch
Launch and support
live
Brief and estimateWe review the task, size the work and put the scope in writing — before the start
StructureSections, page types and visitor journeys — before the first screen is drawn
DesignKey pages at three sizes, with your own copy and photos
DevelopmentFront-end, admin panel and forms; visible on a staging address from week one
Content and checksContent is migrated; speed, forms, languages and phone behaviour are verified
Launch and supportMigration with redirects from the old URLs, team training and watch after launch
WHAT USUALLY GOES WRONG
Why a website project drags on
How it goes
Scope was never fixed, so every new idea adds another fortnight
Copy and photos are promised “next week” for three months running
Feedback lives in chat threads and nobody remembers what was already agreed
The work is only visible at the end — and it turns out the task was understood differently
After launch the contractor disappears, and server access stays with them
How we run it
Scope and stages are written down; changes are estimated separately, not slipped in
The list of required materials is given at the start, with examples and deadlines
Feedback lives in one place with a status: accepted, in progress, declined
A staging address is open from week one — you see exactly what is being built
Code, database and access are handed to you; support is a separate agreement, not a lock-in
WHAT YOU RECEIVE
What the website work includes
Structure and prototypes
A section map, page types and navigation logic, agreed before design.
Design for your content
Key pages on phone, tablet and desktop — with real copy, not filler.
Development and admin panel
The site and a control panel with fields for your domain and role-based rights.
Three languages
Serbian, English and Russian with linked versions and correct markup for search.
Forms and enquiries
Spam protection, notifications to owners and delivery to the CRM with the visit source.
Speed and technical SEO
Image optimisation, clean URLs, a sitemap, markup and correct indexing.
Migration and redirects
Content from the old site and 301 redirects from the old URLs, so rankings survive.
Training and handover
We walk you through the admin panel and hand over code, database and access — the project stays yours.
COMPARISON
A site builder, a CMS template and a site built for the task
Site builder
CMS template
A VMTech project
Time to launch
Days
Weeks
Weeks, in stages
Custom logic and fields
No
Through plugins
Designed for you
Multilingual
Limited
Via an add-on
Built in, with linked versions
Updates and vulnerabilities
Handled by the platform
A dozen plugins, each on its own
A controlled dependency set
What stays with you
An account and a subscription
The site and plugin licences
Code, database, server and documentation
UNDER THE HOOD
What we build on
PHP · CodeIgniterA backend without exotica — another team can maintain itPostgreSQLData with change history and straightforward exportAn admin panel for your processFields and roles matched to how your team works, not a generic builderAsset pipelineMinification, versioning and size budgets — pages do not get heavier over timeTestsAutomated checks of key journeys before every updateServer and backupsEnvironment setup, certificates, backups and monitoring
The domain, the hosting and the accounts are registered to your company. We get access for the work — and you can revoke it at any time without losing the site.
QUESTIONS
What people usually ask
How much does a site cost and what drives the price?
By the number of page types, languages and the systems the site must exchange data with. The gap between a brochure site and a portal with user accounts is not design but the amount of logic behind the screen. We quote after reviewing the task and fix the scope in writing, so “small additions” do not become an endless invoice.
What do we need to prepare?
Copy about the company and services, photos, the logo in source format and a person who decides on content. If the copy does not exist we provide structure and examples — but we will not write it blind on your behalf: it would come out generic.
Will we be able to make changes ourselves?
Yes. Pages are assembled from blocks, text and images change in the admin panel, and metadata is entered there too. We train your team and leave a short guide. Developers are needed for new functionality, not for replacing a paragraph.
What happens to the old site's traffic?
Before the move we list the existing URLs and set 301 redirects to the matching new pages, checking separately those that bring search traffic. After the switch we watch indexing: search engines re-evaluate some pages over weeks, and that is normal.
What does support after launch cover?
System and dependency updates, backups verified by restore, uptime monitoring, bug fixes and small improvements within an agreed allowance. Terms and response times are set out separately, so you know what the monthly fee buys.
A website as a working tool, not a one-off project
The difference between a site that lasts a month and one that lasts years is in the foundation: content structure, access rights, languages and the ability to add a section without a developer.