Service1 of 6
Web and digital platforms
Corporate sites and platforms your team can edit without asking us for every change. The code, the domain and the deployment stay in your company’s name.
- Category
- Web and digital platformsVerified
- Detailed capabilities
- Pending verification
- Engagement models
- Fixed-scope project
- Maintenance and operations retainer
- Block of hours
- Handover record
- Repository · Documentation · Access · Infrastructure in your name
One component, every state
Illustrative diagram. It does not represent any client’s architecture.
Every state
Default
A visible label, help text below and a button with its real name.
- Accessibility
- The label is tied to the field with for and id. The help text is read on entry, linked with aria-describedby.
- Attributes
aria-describedby="help"
Focus
Focus is visible: a 2 px outline with enough contrast against the background.
- Accessibility
- The outline uses :focus-visible and does not rely on the border colour alone. The outline is never removed without a replacement.
- Attributes
:focus-visible { outline: 2px solid }
Error
The message says what is missing and how to fix it, next to the field.
- Accessibility
- aria-invalid marks the field and aria-describedby links the message, which is announced on returning to the field. Colour is not the only cue.
- Attributes
aria-invalid="true" aria-describedby="help error"
Disabled
The field cannot be edited and says why.
- Accessibility
- disabled takes it out of the tab order. The reason stays as visible text, not in a tooltip.
- Attributes
disabled aria-describedby="reason"
Loading
While saving, the button refuses a second submission and the state is announced.
- Accessibility
- The button gets aria-disabled and keeps focus. A role="status" announces that it is saving.
- Attributes
aria-disabled="true" role="status"
Phone
Everything in one column and the button at full width.
- At this width
- Label, field and button stacked. Touch targets of at least 44 px.
Tablet
The field and the button share a line.
- At this width
- The label sits above; the field grows and the button keeps its width.
Desktop
Label and help on the left, field and action on the right.
- At this width
- Two columns aligned with the rest of the form. The container decides the change, not the screen.
Related scope: Contact and lead formsCMS-style editable sections
What it solves
Common situations, not client cases.
- P-01
Nobody on your team can change a line of text on your site without asking a vendor.
What changesEditable sections: your team publishes and fixes content without touching the code.
- P-02
You don’t know whose name your domain, hosting and site code are in.
What changesRepository, domain and deployment in your company’s name from day one.
- P-03
Your site is slow to load and hard to find when someone searches for you.
What changesStructure, metadata and load times reviewed before going live.
What’s included and what isn’t
Included
They present your company, its services and its contact channels, and are built for your team to maintain.
Pages for one campaign, one product or one specific action.
Internal screens to manage the site’s content, requests or data.
Parts of the site your team changes from a content manager, without touching the code.
Forms with clear validation and a defined destination for every request.
Structure, metadata and load times reviewed as a starting point. How visible you are in search does not depend on the site alone.
Not included
Proposal pending approval- EX-01
Reselling hosting or domains
Hosting and domains are contracted in your company’s name and quoted separately.
- EX-02
Native mobile apps
Boundary to be confirmed: for now they are neither offered nor ruled out.
Boundaries proposed for review (A-07). They are not approved exclusions.
What you receive at the end
This is what you receive. Each row shows whether it passes to you, depends on the contract or is not transferred.
KorhyYour company
- Passes to you
- Per contract and model
- Not transferred
Final ownership is set by each project’s contract.
Base · in every service
- EN-01
Repository
The source code and its history, in a repository your company owns.
Passes to you
- EN-02
Documentation
How the system is built, why it was built that way and how to get it running.
Passes to you
- EN-03
Access
Admin credentials and permissions, handed to the people you name.
Passes to you
- EN-04
Infrastructure in your name
Cloud provider accounts in your company’s name. The exact arrangement is set by the contract.
Per contract and model
Specific to Web and digital platforms
- EN-05
Deployment in your name
The site running on your company’s accounts, with instructions to deploy it again.
Passes to you
What is not transferred
Proposal pending approval- NT-01
Our own tools from before the project
Internal accelerators we already had. You use them under a licence; they are not assigned.
Licensed for use per contract
- NT-02
Licensed third-party technology
Services and software from other vendors that the solution uses.
Subject to the vendor’s licence
Engagement models
We don’t publish prices: they depend on the scope. Response times, where they apply, are set in the contract.
| Criterion | AFixed-scope projectEnquire with this model: Fixed-scope project | BMaintenance and operations retainerSelectedRemove: Maintenance and operations retainer | CBlock of hoursEnquire with this model: Block of hours |
|---|---|---|---|
| When it applies | When you need a new site or platform with a clear goal and clear limits. | When the site is already live and needs ongoing care. | When the work is occasional: a new section, a form or a performance fix. |
| How it works | We agree on scope, exclusions, milestones and price before starting. Scope changes are quoted separately. | A monthly fee covers an agreed set of corrective and evolutionary maintenance tasks. | Prepaid hours used task by task, with a log of what was done. |
| Deliverables | Site deployed in your name, documentation and a handover record at the close. | A periodic report of the work done and up-to-date documentation. | Hours log and the documentation for each task. |
| Contract considerations | The price is set in the proposal. Hosting and domains are quoted separately, in your name. | The monthly scope and the SLA are agreed in writing in the contract. | How long the hours stay valid, and on what terms, per the contract. |
- A
Fixed-scope project
- When it applies
- When you need a new site or platform with a clear goal and clear limits.
- How it works
- We agree on scope, exclusions, milestones and price before starting. Scope changes are quoted separately.
- Deliverables
- Site deployed in your name, documentation and a handover record at the close.
- Contract considerations
- The price is set in the proposal. Hosting and domains are quoted separately, in your name.
- B
Maintenance and operations retainer
- When it applies
- When the site is already live and needs ongoing care.
- How it works
- A monthly fee covers an agreed set of corrective and evolutionary maintenance tasks.
- Deliverables
- A periodic report of the work done and up-to-date documentation.
- Contract considerations
- The monthly scope and the SLA are agreed in writing in the contract.
- C
Block of hours
- When it applies
- When the work is occasional: a new section, a form or a performance fix.
- How it works
- Prepaid hours used task by task, with a log of what was done.
- Deliverables
- Hours log and the documentation for each task.
- Contract considerations
- How long the hours stay valid, and on what terms, per the contract.
05Questions
Frequently asked questions
What people ask us most before starting.
It depends on the scope. After the diagnosis we send you a proposal with the scope, timeline and cost. If you go ahead with the project, the diagnosis fee is credited against the proposal.
Yes. The source code, the documentation, the access and the deployment pass to your company at handover. The exact ownership terms are set in each project’s contract.
Your company does, in its own name. Hosting, domains, licences and other third-party services are quoted separately; the proposal lists them before work starts.
If the project includes editable sections, yes: your team publishes and changes content without touching the code. Which sections are editable is defined in the proposal.
Yes. Through a maintenance and operations retainer with an SLA agreed in writing, or a block of hours for occasional changes.
Yes. We can sign a confidentiality agreement and intellectual property agreements covering the deliverables.
Your enquiry
This comes with you to the contact form. The link only carries the service and the model.
- Service
- Web and digital platforms
- Model
- Maintenance and operations retainerRemove or change the model