What Web Development Services Actually Include: A Deliverables-Based Breakdown

TL;DR: Most web development disputes stem from mismatched expectations about deliverables. A proper service package includes five distinct phases: documented discovery (with user flows), interactive design prototypes (not just pretty pictures), semantic development with version control, content migration with SEO preservation, and post-launch training with 30-day support. If your quote doesn’t specify file formats, revision rounds, and response times, you’re buying ambiguity.

The Problem: You’re Buying Hours, Not Outcomes

Last quarter, we inherited a project from a Romanian e-commerce company that spent €8,000 on a “full package” that delivered a WordPress template with their logo swapped in. The agency’s proposal listed “custom development” and “premium design”—but the contract never defined what those terms meant.

This happens because web development services use language that sounds specific but legally means nothing. “Responsive design” is industry standard, not a feature. “SEO optimization” could mean adding a meta description or restructuring your entire information architecture.

The fix? Stop accepting bullet points. Start demanding deliverables.

Phase 1: Discovery and Planning (The Most Skipped Step)

Good agencies spend 20-30% of project time here. Bad agencies skip it entirely.

What you should receive:

• •Technical audit of existing assets (if migrating): Excel sheet listing every URL, redirect mapping, and content inventory
• •User flow diagrams: Actual diagrams showing how different personas navigate from entry to conversion (delivered as Figma/Adobe XD files or Lucidchart exports)
• •Competitive analysis: 3-5 competitor sites broken down by load speed (specific Lighthouse scores), UX patterns, and content gaps
• •Scope document: Technical specifications with database schemas (for custom projects) or plugin compatibility matrix (for CMS builds)
• •Risk assessment: What’s likely to break, what’s deprecated, and contingency budgets for third-party API failures

Red flag: If an agency quotes you a fixed price after a 30-minute call, they haven’t done discovery. They’re guessing.

At MLN.Office, we stopped offering fixed-price quotes without a paid discovery phase. Not because we want to upsell, but because we’ve seen too many projects fail when we discover the client needs multi-language support or GDPR-compliant consent management halfway through build. Discovery costs between €800-1,500 depending on site complexity, but it saves €5,000+ in change orders later.

Phase 2: Design (Wireframes Before Pixels)

Design isn’t decoration. It’s communication architecture.

Deliverables you should get:

• •Low-fidelity wireframes: Black and white layouts showing content hierarchy, not brand colors. These focus on information architecture.
• •Interactive prototypes: Clickable Figma or Adobe XD files that simulate user flows. You should be able to click “Add to Cart” and see the cart update without writing any code.
• •Design system: Typography scales (in rem/em units, not pixels), color hex codes with accessibility contrast ratios documented, and component library (buttons, cards, forms in all states: default, hover, active, disabled)
• •Responsive breakpoints: Designs for mobile (375px), tablet (768px), and desktop (1440px) minimum. Not “it’ll adjust automatically.”
• •Revision rounds: Contract should specify exactly how many rounds (we do 3 major rounds) and what constitutes a “revision” vs. a “new feature request”

The handoff: Design files should be organized with developer-ready assets—exported SVGs, compressed WebP images at 1x and 2x resolution, and CSS variables documented.

Phase 3: Development (Where Promises Become Code)

This is where most clients lose visibility. Demand transparency.

What “clean code” actually means:

• •Version control: Access to a GitHub/GitLab repository where you can see daily commits. If your developer gets hit by a bus, another developer should be able to clone the repo and continue work.
• •Component-based architecture: Whether using React, Vue, or WordPress Gutenberg blocks, the site should be built from reusable components, not one-off pages.
• •Performance budget: Specific metrics—LCP (Largest Contentful Paint) under 2.5s, CLS (Cumulative Layout Shift) under 0.1, TBT (Total Blocking Time) under 200ms. These are Core Web Vitals requirements that affect Google rankings.
• •Security hardening: SQL injection protection, XSS filtering, CSP headers, and automated dependency scanning (using tools like Snyk or Dependabot)
• •Staging environment: A password-protected clone of your site where you can test changes before they go live. URL should be something like staging.yourdomain.com

For WordPress specifically:

• •Custom post types defined for content that doesn’t fit standard posts/pages
• •ACF (Advanced Custom Fields) or similar for flexible content management
• •Caching configuration (Redis or similar) with cache-busting strategies
• •Automated backups to off-site storage (AWS S3 or similar), not just server snapshots

Phase 4: Content Integration (The Hidden Time Sink)

Migrating 500 blog posts manually takes 40 hours. If your contract doesn’t mention content migration, you’re doing it yourself.

What should be included:

• •Automated content migration: Scripts that pull content from old database to new structure, preserving publish dates, authors, and URL slugs (critical for SEO)
• •Image optimization: Bulk compression of existing assets, WebP generation with fallbacks, alt text migration or generation
• •SEO preservation: 301 redirect mapping from old URLs to new structure (delivered as .htaccess or Nginx config file)
• •Schema markup: JSON-LD structured data for articles, products, or local business info
• •Multi-language setup: If needed, WPML or Polylang configuration with hreflang tags properly implemented

Training: You should receive 2-3 hours of screen-recorded walkthroughs showing how to update content, add blog posts, and manage users. Not a 50-page PDF that becomes outdated in three months.

Phase 5: Testing and Launch (Checklists, Not Hope)

Pre-launch deliverables:

• •Cross-browser testing report: Screenshots from BrowserStack or LambdaTest showing the site on Chrome (latest), Safari (latest), Firefox, and Edge, plus mobile Safari and Chrome Mobile
• •Accessibility audit: WCAG 2.2 Level AA compliance check using automated tools (axe, WAVE) plus manual keyboard navigation testing
• •Security scan: SSL configuration check, mixed content detection, and form spam protection testing
• •Load testing: For expected traffic levels (using tools like k6 or Artillery), proving the site handles 100+ concurrent users without crashing
• •Go-live checklist: DNS changeover procedure, email deliverability verification (SPF/DKIM records), and search console submission

Launch day support: Someone should be available 09:00-18:00 (our standard hours) to handle DNS propagation issues or rollback if critical bugs appear.

The Post-Launch Reality (Where Agencies Disappear)

Here’s the truth: 60% of web development agencies in Romania don’t answer support tickets two months after launch.

What should be included in your first 30 days:

• •Bug fixes: Actual code defects, not “I changed my mind about the color”
• •Performance monitoring: Weekly Core Web Vitals reports showing if the site slows down as real users hit it
• •Analytics setup: Google Analytics 4 or Plausible configured with conversion tracking, not just pageview code
• •Documentation: Technical documentation listing server credentials, plugin licenses, and third-party API keys

Maintenance packages (usually monthly):

• •Security updates within 24 hours of critical CVE releases
• •Weekly backups stored off-site (we use AWS Dublin region for Romanian clients)
• •Uptime monitoring with SMS alerts if the site goes down
• •Content update allowance (typically 2-4 hours/month for text changes)

How to Evaluate Proposals: A Practical Checklist

When comparing quotes from MLN.Office versus other agencies, look for these specificity markers:

Instead of: “Custom responsive design”
Look for: “Interactive Figma prototypes with 3 revision rounds; HTML/CSS using Bootstrap 5 or Tailwind; tested on iOS Safari and Android Chrome”

Instead of: “SEO friendly”
Look for: “Schema.org markup for LocalBusiness; XML sitemap auto-generation; Core Web Vitals optimization targeting LCP <2.5s; 301 redirect mapping for URL changes”

Instead of: “Fast loading”
Look for: “Redis object caching; Cloudflare or BunnyCDN setup; image optimization pipeline converting uploads to WebP; lazy loading implementation”

Instead of: “Training included”
Look for: “Two 60-minute Loom video walkthroughs covering content editing and user management; written documentation in Google Docs with your specific admin credentials”

Trade-offs and Limitations

Template vs. Custom: A €2,000 WordPress template build gets you online in two weeks. A €15,000 custom build gets you optimized conversion flows and unique functionality. Most Romanian SMEs don’t need custom—they need a well-configured template with proper caching.

Fixed price vs. Time-and-materials: Fixed price protects your budget but limits flexibility. We often recommend hybrid: fixed price for discovery + design, time-and-materials for development (since that’s where unknowns live).

Scope creep is usually discovery failure: If you “suddenly” need a booking system halfway through the project, that’s not scope creep—that’s incomplete requirements gathering. Good agencies charge for discovery to prevent this.

Technical debt: Cutting testing to save €1,000 means you’ll spend €3,000 fixing bugs in six months. There’s no such thing as a cheap website—only delayed costs.

Conclusion

Web development services shouldn’t be a black box. You should know exactly what files you’re receiving, what metrics the site must hit, and who’s responsible when something breaks.

The difference between a €3,000 website and a €13,000 website often isn’t the visual design—it’s the invisible infrastructure: redirect mapping that preserves your SEO, automated backups that save you when a plugin update crashes the site, and documentation that lets you fire your agency without losing access to your own platform.

Before signing any contract, ask: “Can you show me the last project’s GitHub repository and staging environment?” If they hesitate, keep looking.

Ready to see what transparent development looks like? We document every phase. Let’s talk: Contact MLN.OFFICE.

Further Reading

• •Web Content Accessibility Guidelines (WCAG) 2.2 - Official W3C accessibility standards
• •Google Core Web Vitals - Performance metrics documentation
• •ANSPDCP Guidelines - Romanian data protection requirements for websites
• •MDN Web Docs: Responsive Design - Technical implementation standards
• •GitHub Guides - Understanding version control deliverables