Web Design & Software

A corporate website is most customers' first contact with you. That first contact answers two questions: what does this company do, and can it be taken seriously. Both are matters of content and speed before they are matters of design.

So we start not with a visual mockup but with what the page needs to say.

Scope

• Corporate websites — company presentation, service pages, a content section, contact flow
• Custom software — internal systems, panels, calculation and reporting tools for processes off-the-shelf products do not cover
• Modernizing existing systems — gradual renewal of software that works but has aged
• Performance and technical SEO — speed, mobile behavior, the technical side of search visibility
• Accessibility — keyboard operation, screen reader compatibility, sufficient color contrast

Speed is part of the design

A slow page is not a well-designed one. If the user leaves while waiting for an image, the aesthetics cannot even be assessed.

What makes the difference in practice is unglamorous: serving images at resolutions matched to the screen, not loading unnecessary scripts, loading fonts without blocking, prioritizing what appears first.

This site is built on the same principles — it grew from a single promotional page into separate content and service pages, and its styles were consolidated into one cacheable file.

Custom software: not everything should be written

If an off-the-shelf product covers a task, writing custom software wastes money and time. In areas like accounting, email and file sharing, existing solutions are more than mature.

Custom software makes sense where you do the work differently from your competitors. Your own pricing logic, your own production flow, your own approval chain — those get written when they do not fit an off-the-shelf product.

We make that distinction at the start of the conversation. Sometimes the conclusion is "this does not need software" — saying so is part of the job.

What we hand over

• The complete source code and operating documentation
• Domain, server and third-party accounts opened in your name
• Acceptance criteria written into the contract — so there is no argument over "delivered"
• Handover support for your team during transition

We set out why these belong in the contract in our article on technology contracts.

How we work

We begin with a short discovery: who comes to the page, what they are looking for, and which action you want them to take. The answers to those three frame the design.

After that we show a working version early. Comments made on a screenshot differ from comments made while moving through a real page — the second kind is more accurate.