Three months ago, an accounting firm came to us with a problem. Their existing website - a premium WordPress theme they'd paid someone to "customize" - loaded in 6.8 seconds, couldn't handle more than 20 concurrent users, and had a contact form that broke every time WordPress auto-updated. They were paying 50 EUR per month for a "maintenance plan" that mostly consisted of someone clicking "Update All" in the plugin dashboard and hoping nothing caught fire.
We rebuilt their site from scratch. Hand-coded frontend, headless CMS for their blog, a secure client portal where customers could upload tax documents. Load time: 1.1 seconds. Monthly maintenance cost: roughly a third of what they were paying before. The site has been running for 11 months now without a single outage or broken feature.
That's the difference between a template site and a custom build. Here's how we actually do it.
Phase 1: Discovery - Asking the Hard Questions
Every project starts with a discovery call, and we should warn you upfront: we ask uncomfortable questions. Not about colors and fonts - about your business.
We want to know: What does your website need to accomplish? Not "look professional" - that's table stakes. We mean specifically: Are you generating leads? Selling products? Reducing support calls? Building authority in your industry?
We had a restaurant client in Tuzla who initially told us they needed "a nice website with their menu." Thirty minutes into the discovery call, it turned out their real problem was that 60% of their phone orders were getting details wrong - wrong toppings, wrong sizes, wrong delivery addresses. What they actually needed was an online ordering system that reduced errors and freed up their staff. The "nice website with menu" was just the surface.
What We Map Out in Discovery
- Business goals and KPIs: What does success look like in 6 months? We need numbers, not feelings.
- User journeys: Who visits your site, what do they need, and what's the shortest path to giving it to them?
- Technical requirements: Do you need a CMS? E-commerce? Integrations with existing tools (CRM, accounting software, booking systems)?
- Content inventory: What content do you have? What needs to be created? Who's writing it?
- Competitive landscape: We analyze 3-5 competitors' sites. Not to copy them - to understand what your audience already expects and where you can differentiate.
This phase takes 1-2 weeks depending on complexity. We deliver a project brief that both sides sign off on before any design work begins. This document has saved us from scope creep disasters more times than we can count.
Phase 2: Wireframing and Information Architecture
Before anyone opens a design tool, we map out every page's structure in low-fidelity wireframes. Gray boxes, placeholder text, no styling. This forces everyone to focus on what matters: information hierarchy and user flow.
We use simple tools for this - sometimes just pen and paper sketches that we photograph and annotate. The goal isn't a pretty deliverable; it's alignment on structure before we invest design hours.
Why This Step Saves Thousands
A client who runs a chain of dental clinics skipped wireframing with their previous agency. The agency went straight to high-fidelity mockups. The designs looked stunning - and were completely wrong for the user flow. Patients looking for emergency contact info had to scroll through three screens of stock photography and mission statements. By the time the client realized the problem, the agency had already built half the site. Fixing it cost an additional 3,000 EUR.
With wireframes, restructuring costs nothing. Moving a gray box takes 30 seconds. Moving a fully designed and coded section takes hours.
We typically deliver 2-3 wireframe iterations before moving to visual design. Each iteration incorporates client feedback and usability testing - we'll often put wireframes in front of 5-10 real users (friends, family, actual customers) and watch where they click first, what confuses them, and how quickly they find key information.
Phase 3: Visual Design
Now we make it look good. But "look good" isn't subjective at our shop - it means: visually communicates your brand, guides the eye to important elements, works across every screen size, and follows accessibility standards.
We design mobile-first. Not because it's trendy, but because over 65% of the traffic we see across our client portfolio comes from mobile devices. If your site doesn't work beautifully on a phone, you're alienating two-thirds of your audience.
Our Design Principles
- Typography does the heavy lifting. We spend more time choosing and pairing fonts than picking colors. Good type hierarchy means users understand your content structure without reading a word.
- Whitespace is a feature, not wasted space. Cramming every service, testimonial, and call-to-action above the fold doesn't work. It overwhelms. We give content room to breathe.
- Every decorative element earns its place. If an animation, gradient, or image doesn't serve comprehension or conversion, it gets cut. We had a real estate client who wanted a full-screen video background on their homepage. We tested it: the video increased load time by 3.2 seconds and decreased engagement by 18%. We replaced it with a high-quality static image with subtle parallax. Engagement went up, bounce rate dropped.
- Accessibility isn't optional. WCAG 2.1 AA compliance minimum. Proper contrast ratios, semantic markup, keyboard navigation, screen reader compatibility. Roughly 15% of the global population has some form of disability. That's not a niche - that's a market segment larger than most countries.
Clients receive 2-3 design concepts for the homepage and one key interior page. Once the direction is chosen, we design remaining templates. Total design phase: 2-4 weeks.
Phase 4: Development - Where We Diverge from Most Agencies
Here's where our process differs dramatically from the "install WordPress, buy a theme, add plugins" approach that dominates the market.
We don't use WordPress templates. We don't install 30 plugins and pray they all play nice together. Every site we build is hand-coded or built on a headless CMS architecture, depending on the client's content management needs.
Our Technology Decisions
For most business websites, our stack looks like this:
- Frontend: Semantic HTML, Tailwind CSS, vanilla JavaScript or a lightweight framework. No jQuery. No Bootstrap. No 400KB of unused CSS.
- CMS (when needed): Headless options like Strapi or a simple custom admin panel. The client gets an intuitive editing interface; the frontend stays fast and secure.
- Backend: PHP or Node.js depending on requirements. Clean API architecture for any dynamic features.
- Hosting: Optimized server configuration specific to the tech stack. Not "throw it on a shared server and hope for the best."
A restaurant client who needed online ordering got a custom order management system that integrated with their existing POS terminal. A logistics company got a shipment tracking portal that pulled real-time data from their fleet management API. An accounting firm got a secure document upload system with client authentication and encrypted storage.
None of these would work with a WordPress template and WooCommerce. They needed custom engineering, and that's what we deliver.
Performance Is Not Optional
Every site we build targets these benchmarks before launch:
- PageSpeed score: 90+ on mobile (most of our sites hit 95+)
- Largest Contentful Paint: Under 2.5 seconds
- Cumulative Layout Shift: Under 0.1
- First Input Delay: Under 100ms
- Total page weight: Under 500KB for initial load (excluding user-uploaded images)
We've seen agencies hand off sites with 4MB homepages that score 35 on PageSpeed and call it "done." That's not a website - that's a liability.
Phase 5: Testing - Breaking Things on Purpose
Before any client sees the staging site, we've already tried to break it.
Our Testing Checklist
- Cross-browser testing: Chrome, Firefox, Safari, Edge. Both desktop and mobile versions. Yes, Safari still renders things differently, and yes, we still have to account for it.
- Device testing: Real devices, not just browser resizing. We test on actual iPhones, Android phones, iPads, and various screen resolutions. Emulators miss things - touch targets that are technically "tappable" but practically impossible on a real thumb, for instance.
- Performance testing: Load testing with simulated traffic. We verify the site handles 10x the expected concurrent users without degradation.
- Security audit: SQL injection attempts, XSS testing, CSRF verification, authentication bypass checks, file upload validation. We had a penetration tester find an edge case in a file upload feature during testing once. Took us 20 minutes to fix. If it had been found in production, the client's data could have been exposed.
- Form testing: Every form is submitted with valid data, invalid data, empty data, special characters, and excessively long input. We test email deliverability to ensure contact form submissions actually arrive.
- SEO verification: Proper meta tags, Open Graph data, structured data markup, sitemap generation, robots.txt configuration, canonical URLs.
Testing typically takes 3-5 days. We fix everything found. Then we test again.
Phase 6: Launch Day
Launch day at our office is methodical, not dramatic. We've done this enough times that it's a checklist, not an adventure.
The Launch Sequence
- Final client approval on staging environment
- DNS TTL lowered to 300 seconds (24 hours before cutover)
- Production environment provisioned and hardened
- Database and files migrated from staging to production
- SSL certificates installed and verified
- DNS records updated
- CDN configured and cache warmed
- Analytics and tracking codes verified
- Monitoring alerts activated
- Final spot-check of all critical pages and functions
We schedule launches for Tuesday or Wednesday mornings. Never Fridays - if something unexpected surfaces, we want a full workweek ahead of us, not a weekend.
Phase 7: Post-Launch - The Part Most Agencies Skip
Launching a website isn't the finish line. It's the starting line.
For the first 30 days, we monitor performance metrics daily. We watch real user behavior through analytics - where do people actually click? Where do they drop off? Are the conversion paths we designed actually working?
We had a B2B client whose beautifully designed "Request a Quote" form was getting almost no submissions. Analytics showed users were reaching the form but abandoning it. The problem? We'd included 12 form fields. We reduced it to 5 essential fields and added a second step for details. Submissions increased by 140% in the first month.
Every client gets 30 days of post-launch support included. Bug fixes, content adjustments, performance tuning - all covered. After that, we offer ongoing maintenance plans that include security updates, performance monitoring, content updates, and quarterly optimization reviews.
What This Costs (Honest Numbers)
A custom website from our team starts at around 1,500 EUR for a straightforward business site (5-7 pages, contact form, responsive design, basic SEO). More complex projects - e-commerce, client portals, custom integrations - range from 3,000 to 12,000+ EUR depending on scope.
Is that more than a WordPress theme? Yes. Is it worth it? Every single client who's come to us after struggling with a template site says the same thing: "We should have done this from the start."
Templates are fine for a personal blog or a hobby project. But if your website is a business tool - if it needs to generate revenue, capture leads, or serve customers - it deserves engineering, not assembly.
That's what we build. And we've been building it for over two decades.