Content.
What should the website explain?
Pages, copy, languages and existing material determine how much needs to be planned, designed and built.
Scope / Work / Proposal
The task first.
The price follows.
A business website, custom software and analysis of existing programs require different work. You receive a specific proposal for your project, with a defined scope and clear deliverables.
The first assessment is free and without obligation.
What shapes the work
Five considerations.
The right scope.
Features.
What should the solution do?
A contact form requires different work from a portal with user roles, approvals and custom business rules.
Existing systems.
What information is available?
Existing systems, data formats and documentation shape the integration work. If necessary interface information is missing, the scope of analysis and any necessary decompilation within section 69e UrhG is defined in advance.
Design.
How distinctive should it be?
Visual concepts, distinctive interactions and elaborate animation are planned to suit the goal and budget.
Operations.
What happens after handover?
Hosting, content editing, technical maintenance and ongoing support are clearly described and itemised when included.
The proposal
Know what will be built.
What it will cost.
And what is included.
Deliverables, assumptions, your input and the agreed handover are set out in writing. This includes whether the brief covers a website, an application with APIs or analysis with documented findings. Where several approaches make sense, the proposal can compare options.
The route to a proposalCommon questions
Good to know
before you enquire.
Why are there no package prices?
The right scope depends on your content, features and existing systems. A specific proposal describes the work actually needed.
Can I share a budget range?
Yes. A budget range helps prioritise work and assess different approaches. The scope is still clarified together.
Are hosting and maintenance included?
Both can be part of the agreement. Responsibilities and any ongoing costs are set out in the proposal.
What about rights and source code?
Usage rights, access and source-code handover are defined in the project proposal.
What happens if requirements change?
New requirements are reviewed together. Additional work and any impact on price and timing are agreed before implementation.
An easy way to start
A challenge.
A first conversation.
What do you want to achieve? What already exists? A few sentences to Lukas Richter are enough for a free first assessment.
Describe your project