A simpler project
A company website, a redesign, a sales website or one specific feature. We start with a short conversation, then you get a written proposal and a fixed price for the agreed scope.
How I work
Bring me the problem, not a specification.
I’m an engineer by training with about three years of professional experience. For about a year and a half I’ve worked in sales management, leading a large sales team, and I built HelpTravel from scratch and keep developing it. So I start with how your business sells and where it loses time. Design and code come after that.
What you can count on
I understand sales
I know what customers actually buy, how a sales team works and where enquiries get lost. The website should help that team, from a customer’s first visit to the first conversation.
I run the whole project
Analysis, offer and copy, design, code, integrations, launch and the support we agree on after it. You talk to me directly throughout.
I think like a product owner
I develop HelpTravel with real users, so I also design for what happens after launch: day-to-day operation, changes and further development.
Custom design, real code
I don’t install ready-made templates. If an existing platform such as Shopify makes more sense than code from scratch, I’ll tell you so.
How a project runs
01
Conversation
About your business, your customers and what should work better.
02
Written proposal
The scope, the stages and a fixed price for the agreed scope.
03
Design and build
Content and direction first, then code. Feedback happens at agreed points.
04
Launch and support
Going live and fixing bugs for an agreed period.
A complex system may start with a paid analysis stage. You keep the result.
Most businesses need a really good website. If yours needs more, I’ll tell you plainly.
How we get to scope and price
I don’t have a price list or packages. A sales website and a web system can differ in scope enormously, so I get to know the project first and then prepare a specific scope and quote.
A complex system
Bookings, larger integrations, custom tools or a web product may start with a paid analysis stage. It gives you a description of how the system works, the main flows, the scope, integrations, constraints and risks, the delivery stages and a basis for the quote. You keep the result, and if we build the project together, the cost of the analysis can be credited towards it.
What I always bring
- an understanding of the business and its customers
- a clear decision on what the website or system must do
- the content structure and the main sales copy
- the visual direction and a design for phone and desktop
- the build and the integrations it needs
- testing on phones, desktops and the main browsers, accessibility, speed and technical SEO basics
- launch and bug fixes for an agreed period
What I deliberately don’t do
- brand identity and logos from scratch
- photo and video shoots
- ad campaigns and social media management
- ongoing SEO campaigns
- native mobile apps
- installing ready-made templates and nothing more
What I can do is plan which materials are needed and how they will be used, work with your materials and set the visual direction of the site.
Questions people usually ask
How much does it cost?
The price depends on the scope, which is why I don’t have a price list or packages. After our conversation you get a written proposal with the stages and a fixed price for the agreed scope.
How long does it take?
That depends on the scope too. The timeline and stages are in the written proposal before anything starts.
What do I need to prepare?
A short description of your business and what should change, access to your current website and materials if you have them, and a person who can make decisions.
When will I see what it looks like?
Before I build anything, I show you the content structure, the main copy and the visual direction. I collect your feedback at agreed points: after the direction, after the first working version and before launch.
Will you write the copy?
The content strategy and the main sales copy, yes, that’s part of the project. Hundreds of product descriptions, bulk content migration, a whole blog or specialist legal texts aren’t included automatically. We agree the content scope together with the project scope.
Can I edit the content myself later?
Where it makes practical sense, for example your offer, case studies, articles or prices, I design a convenient way to change it. I don’t add an admin panel without a reason.
Who owns what gets built?
You get the rights to the materials and code created for your project, to the extent they can be transferred. Libraries, fonts, stock photos, SaaS services, APIs and other providers’ platforms stay under their own licences.
What happens after launch?
For an agreed period I fix bugs that come from the build. New features, new content and changes of scope are separate work, quoted separately.
What this looks like in practice
Let’s talk about your business.
Call or send an email. One sentence about what should work better is enough.
Leave a short message