Conversation and scope
We get to know your business, everyday processes and the people who will use the website or application. We agree content, functionality and materials.
You do not need to arrive with technical requirements. We start with your needs, show you a proposal you can try in a browser and agree the scope before developing the functionality.
An HTML prototype is an early version you can open in a browser. You can review the design and content, explore the navigation and try the proposed interactions before we build the working features.
We send the prototype by email as a link or a file. You can review it at your own pace, show colleagues and gather comments before we develop the agreed functionality.
This helps us notice missing information, unnecessary steps or a proposed workflow that does not suit you earlier.
Choose a stage to see what we show
in a prototype and what we develop for actual use.
We agree which fields are needed, what the button says and what confirmation a visitor sees. We can also show example error messages.
We implement input checks, protection against unwanted messages and delivery to an agreed address. We include inquiry storage in a database when it is part of the agreed scope.
Illustrative example. Nothing is sent here.
We get to know your business, everyday processes and the people who will use the website or application. We agree content, functionality and materials.
We prepare a proposal you can open in a browser. We bring comments together and agree changes. The quote states how many revision rounds are included.
We build the agreed functionality and check the presentation, forms, data and permissions included in the project. We review the final version together.
We agree which code, access and instructions to hand over and how the project will go live. Maintenance, support and future improvements are agreed separately according to the project’s needs.
We create the interface in HTML, CSS and JavaScript, and use Laravel to develop functionality and business logic. Laravel is a development framework that provides established foundations for applications.
We adapt the code we develop to each project. We do not build websites in WordPress or visual editors such as Elementor. We use Adobe Photoshop to process photographs and prepare graphic materials.
This approach gives us control over implementation and future improvements. Speed and quality depend on good development, optimization and maintenance, so we check them on the actual project.
Yes. We use AI to support preparation and development. Decisions about how a website or application works, implementation checks and responsibility for the delivered work remain with us. We explain preparation for AI search separately on our SEO and AI search page.
Our approach is based on project-specific code and Laravel for functionality and business logic. It suits our customization and ongoing development work. WordPress can be a good choice for other needs; technology alone does not determine a website's quality.
No. A simple presentation website may need very little functionality. We develop data storage, administration and integrations when they are needed and included in the quote.
We can prepare a simpler proposal quickly when the scope and materials are clear. We agree a schedule for each project. The prototype is followed by agreement on revisions, functionality development and final checks.
Quotes may include different numbers of pages, content preparation, revisions, administration, integrations and support. Our quote states what we build, what you provide and what costs extra, so you can compare the actual scope.
We can continue with hosting, maintenance and improvements, and you can also choose another provider for these services. We discuss that choice from the outset.
The contract defines what you receive at handover: the agreed source-code version, access and instructions, together with the rights to use and modify the code and continue with another contractor.
We distinguish between code created for your project, our existing components and third-party libraries. The documentation records their licences and your agreed usage rights, so you know the conditions for using and continuing to develop the project. We may reuse shared components in other projects.
Handover of the agreed source-code version, an overview of technologies and dependencies, and setup and usage instructions appropriate to the project scope.
Handover or changes to the appropriate access credentials and the agreed data export. We separate access to a client project from access to our shared infrastructure.
If you move to another contractor or host, we agree timing, the transfer process and who takes over technical care. We estimate any additional migration work before it begins.
Regular maintenance and new improvements are separate services. The quote and contract define how defects in the agreed delivery are corrected.
How do we separate monthly costs?Tell us about your business and what you need.
You don’t need all the answers before our first conversation.