Content · usability · code · visibility
Websites and applications that guide customers to a decision.
We build websites, client portals and web applications that organise information, simplify decisions and lead to the right action. The domain, data and key accounts remain under customer control.
Four delivery formats
From a simple business card to a dedicated system.
The scope grows with the real need. We do not add a portal, database or API when a simpler solution can achieve the objective.
One-page business website
A single scrolling page presenting the company, key services and contact details. Suitable for a concise offer without a complex structure.
- everything on one page
- clear mobile view
- form or direct contact
Standard business website
A service with separate offer pages, a gallery or projects and a structure prepared for future development.
- navigation and subpages
- gallery, projects or news
- technical SEO and optional PL/EN
Website with a client portal
A public website connected with a protected area where the customer uses the agreed service modules.
- accounts, roles and secure login
- documents, requests or chat
- activity history and notifications
Web application / mini CRM or ERP
A dedicated system for customers, tasks, documents, billing or a selected business process. An API is added when the application needs to exchange data with other systems.
- workflow tailored to the business
- roles, data and reporting
- integrations and dedicated API
Example modules
What can be combined in one solution.
This is a catalogue of possibilities, not a ready-made package. We select only the modules required by the process and establish which data and integrations are genuinely justified.
Customer self-service
- online appointment booking
- user account or client portal
- requests, complaints and case status
- secure documents for download
- email or SMS notifications
Employees and work organisation
- employee portal and schedule
- tasks, deadlines and accountability
- approval and document workflow
- knowledge base and procedures
- roles and access scope
Sales and billing
- mini-CRM customer database
- quotation calculator or generator
- orders and fulfilment status
- receivables, payments and reminders
- reports and PDF or Excel export
Data and integrations
- management dashboard and KPIs
- calendar integration
- email or SMS connection
- accounting or ERP data exchange
- dedicated API for other systems
From information to secure deployment
A website should guide a customer from a question to contact.
We do not begin with a feature list. We first shape the three moments that determine whether a visitor stays, trusts the business and takes the next step.
The first 10 seconds
“Is this offer relevant to my problem?”
We organise the headline, value and audience so that the answer is visible without searching.The trust moment
“Is this business specific and responsible?”
We show the real scope, limitations, way of working and credible information instead of marketing shortcuts.The next step
“What should I do now?”
We create a straightforward route to contact, a quotation or the relevant service, without distracting decisions on the way.Control and accountability
The project should remain useful after it launches.
A website or application is a business asset, not leverage held by a supplier. Before launch, we define ownership, access, maintenance and accountability boundaries.
- 01The domain, hosting and key accounts are held by the customer or transferred under explicit terms.
- 02Code, libraries, images and fonts have a known source and permitted use; we do not imitate another system in code or headers.
- 03Forms and portals receive agreed safeguards, data minimisation and safe error handling.
- 04Before launch, we test the agreed scope: mobile, keyboard, forms, links, performance, PL/EN and indexing.
- 05Google positions also depend on the market and ongoing work; we provide sound technical and content foundations.
How the work proceeds
Decisions first. Design second. Code last.
Each stage ends with clear material for approval, so the business sees the direction before costly delivery begins.
- 01
Objective and scope
We establish audience, problem, content, integrations, accountability and success criteria.
- 02
Map and prototype
We show structure, key views and messages before the main code is produced.
- 03
Design and build
We build the agreed interface, forms, integrations, SEO and security mechanisms.
- 04
Testing and handover
We verify operation, accessibility, language versions, indexing, backup and future maintenance model.
Clear boundaries
A website requires cooperation on content, rights and maintenance.
Sigma Vision scope
Analysis, architecture, UX/UI, implementation, configuration, technical SEO, testing and deployment stated in the proposal.
Customer responsibility
Offer accuracy, rights to supplied materials, content approval, required sector information and timely decisions.
Quoted separately
Extensive brand identity, photo or video production, specialist translation, legal opinions, paid campaigns, complex integrations and continuous content editing.
FAQ
Questions before building a website or web application.
Cost and timing depend primarily on unique views, content readiness, integrations, content-management model and required testing depth.
Must the website use WordPress?+
No. Technology is selected around functions, update model, hosting, security and maintenance cost. Where WordPress is used, it is an explicit architectural component; where a custom solution is built, it does not imitate WordPress or another product.
Who owns the domain, code and accounts?+
The domain and key accounts should remain under customer control. Rights to code, design and materials and handover rules are defined in the proposal or agreement, taking third-party component licences into account.
Do you guarantee first place in Google?+
No. No supplier can credibly guarantee a particular position in an independent search engine. We provide agreed technical foundations, structure, indexability, performance and content; results also depend on competition, domain history and ongoing work.
Will the website work on mobile and with a keyboard?+
We design responsively and test basic keyboard operation, focus, readability, navigation and horizontal overflow. A specific accessibility standard or formal audit must be stated in the scope.
Will you prepare terms and a privacy policy?+
We can implement supplied text and describe technical data processing, but do not replace legal counsel or a data protection officer. Documents requiring an individual legal opinion should be approved by the appropriate specialist.
What happens after launch?+
We identify the hosting owner, backups, monitoring, updates, form handling and change-request route. Ongoing care is not automatically part of a one-off build unless included in the proposal.
First step: a short scope
Let us establish whether you need a website, portal or application.
Share the current website or briefly describe the process that needs to work better. We will indicate the simplest sensible direction, dependencies and next steps.
Discuss the web project →