Choose whether to allow Google analytics and advertising cookies. The website and forms work without them.
Optional Google tags help us measure visits and advertising. Choose what you allow. The website and enquiry forms work without these cookies.
Your previous Google Analytics opt-out remains active.
DesignJust4You · Digital solutions for business
A presentation website explains your offering. A web application lets a user complete a task: submit a request, book an appointment, check a status, enter data or download a document. It runs in a web browser, and we define access methods and supported devices according to the users and working environment.
One example is a portal where a client submits a request and documents, an employee checks the data and changes the status, and the client tracks the next step in their account. This is an example of functionality we can plan, rather than a predefined package.
Accounts, documents, requests and an overview of the working relationship.
Appointments, capacity, confirmations and cancellation rules.
Records, tasks, work orders and approval workflows.
Catalogues and ordering with customer-specific terms.
Core functionality for testing an idea with real users.
A CMS is a system your team uses to edit content. When a standard system does not cover the types of data or publishing rules you need, we can develop a tailored administration area.
A custom CMS can include multiple content types, a catalogue with related data, editor roles, approval before publication and multilingual content management. We adapt input forms to the team: editors get the fields they need for their work, with clear rules and input validation.
For many presentation websites and blogs, an existing CMS is a good choice. Custom development makes sense when content, workflow or integration requirements exceed the capabilities of a standard solution. During the initial analysis, we compare the scope, maintenance and extension options of both approaches.
DesignJust4You / Project guide
Who has access and what task do they need to complete?
Key screens, rules and feedback.
Features, integrations and access checks.
Environment, documentation and a maintenance plan.
Example workflow. The specific scope depends on the project.
From the first user task to a tested browser-based application.
We first describe user steps and prepare key screens. Once the scope is agreed, development proceeds in functional stages. Testing covers the agreed workflows, access rights, behaviour on different devices and data exchange. We plan implementation together with the system's users.
The quote depends on the number of roles, screens, rules, integrations and the migration of existing data. We estimate timing after the specification. We list hosting, external services and maintenance costs separately in the quote so the total investment is clear.
For an application to be useful, testing should follow real user tasks. For a booking, for example, we check appointment selection, changes, cancellation and what happens when two people try to book the same capacity. For a CMS, we check content entry, preview and publication across different editorial roles.
We agree on supported devices and browsers, problem reporting and acceptance criteria. Clear field labels, error explanations and keyboard operation are part of accessibility planning. A useful framework for these requirements is provided by the W3C WCAG guidelines.
If the application manages customers or operations, also explore CRM and ERP systems. To exchange data with existing programs, we plan API integrations with clear responsibility for data. Before implementation, we define access, training, backups and maintenance so users know how to continue their day-to-day work.
Yes, subject to checking the technology and integration options. The application can have its own account and administration area or share some data with an existing system.
Yes. During planning, we distinguish the first version from later phases. We estimate subsequent scope and cost according to new requirements and the existing architecture.
Project scope, screens and the work behind each solution.
Business web application · Customer portal
Explore the Livsmedelsstädarna application: field tasks, hygiene inspections, corrective work and customer approvals across phones, tablets and computers.
Explore the project
Business web application · Field work
Explore Kore: a phone-friendly distribution application with loading, store deliveries, returns, barcode scanning and operational reports.
Explore the project
Client portal · Demo preview
Explore the Certiwa portal for client and consultant collaboration: ISO documents, review statuses and revisions. The public demo uses fictional data.
Explore the project
In-house system · Public demo
Explore our Azur Travel system demo: travel search, offers and administration. A connected public catalogue and workspace for travel agencies.
Explore the project