Service2 of 6
Full-stack product development
We turn one of your business processes into a web application, from the interface to the database. The code and the data model are documented and in your name.
- Category
- Full-stack product developmentVerified
- 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
A request through the application
Illustrative diagram. It does not represent any client’s architecture.
Request POST /requests
- InterfaceForm and views in the browser
- Validation
- APIInput contract, session and permissions
- Authorization
- Validation
- DomainProcess rules, free of technical detail
- Business rule
- DatabaseData model and transactions
- Data constraint
Response: 201 Created, with the request and its status.
Every state
Create
The request crosses all four layers and returns with the purchase request saved.
- Request
POST /requests- Checks
- Interface · Validation: Flags empty fields before sending. It is help, not security.
- API · Authorization: The session is valid and the role may create requests.
- API · Validation: The body matches the schema: everything is validated again.
- Domain · Business rule: The request starts as a draft, owned by whoever creates it.
- Database · Data constraint: It is saved in a transaction; keys and required fields hold.
- Response
- 201 Created, with the request and its status.
Read
Access to that specific request is authorized before it is read.
- Request
GET /requests/{id}- Checks
- API · Authorization: Being signed in is not enough: the person must be allowed to see this request.
- Domain · Business rule: Decides which fields each profile sees.
- Database · Data constraint: The query filters by the person’s area; nothing extra is fetched.
- Response
- 200 OK, with only the permitted fields.
Invalid data
The API rejects the request; the domain and the database are never touched.
- Request
POST /requests- Checks
- Interface · Validation: The form would have flagged it, but the request came in directly: the interface is not a security boundary.
- API · Validation: The schema fails: the amount is missing and the date is not valid.
- Response
- 422 Unprocessable, with one error per field to show next to each.
No permission
Authorization fails at the API and the request goes no further.
- Request
POST /requests/{id}/approve- Checks
- API · Authorization: Whoever created the request cannot approve it.
- Response
- 403 Forbidden, and the attempt is logged.
Related scope: APIsDatabasesRoles and permissionsBusiness flows
What it solves
Common situations, not client cases.
- P-01
A key process in your company lives in spreadsheets and emails that nobody brings together.
What changesAn application with defined roles and flows, on a documented database.
- P-02
Your tools don’t talk to each other, so someone copies data across by hand.
What changesAPIs that connect the systems and log every exchange.
- P-03
Only the person who wrote your current application understands it.
What changesCode, data model and decisions documented so another team can pick it up.
What’s included and what isn’t
Included
Applications used in the browser to run one of your company’s processes.
Documented interfaces so your application can exchange data with other systems.
The data model and the database that stores it.
Sign-in and account management for the people who use the application.
What each profile can see and do, defined with you.
Panels with the information your team needs to make decisions.
The steps, approvals and states of a process, carried over into the application.
Not included
Proposal pending approval- EX-01
Hardware or firmware development
Not offered.
- 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 Full-stack product development
- EN-05
Deployment in your name
The application running on your company’s accounts.
Passes to you
- EN-06
Documented data model
The database’s entities, relationships and rules, explained for whoever maintains it.
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 retainerEnquire with this model: Maintenance and operations retainer | CBlock of hoursSelectedRemove: Block of hours |
|---|---|---|---|
| When it applies | When you want to turn a specific process into an application, with a clear goal. | When the application is already in production and needs ongoing care and improvement. | When you need occasional changes or a review of an existing application. |
| How it works | We agree on scope, exclusions, milestones and price. We build in cycles, with a preview at the end of each one. | 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 | Deployed application, documented data model and a handover record at the close. | A periodic report, delivered changes and up-to-date documentation. | Hours log and the documentation for each task. |
| Contract considerations | The price is set in the proposal. Scope changes are quoted separately. | 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 want to turn a specific process into an application, with a clear goal.
- How it works
- We agree on scope, exclusions, milestones and price. We build in cycles, with a preview at the end of each one.
- Deliverables
- Deployed application, documented data model and a handover record at the close.
- Contract considerations
- The price is set in the proposal. Scope changes are quoted separately.
- B
Maintenance and operations retainer
- When it applies
- When the application is already in production and needs ongoing care and improvement.
- How it works
- A monthly fee covers an agreed set of corrective and evolutionary maintenance tasks.
- Deliverables
- A periodic report, delivered changes 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 you need occasional changes or a review of an existing application.
- 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.
With a diagnosis: we look at your goal, the current process and its constraints. Then we send you a proposal with the scope, exclusions, milestones and cost.
Yes. The source code, the documentation, the data model and the access pass to your company at handover. The exact ownership terms are set in each project’s contract.
Your company does, in its own name. Infrastructure, licences and other third-party services are quoted separately; the proposal lists them before work starts.
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.
06Next step
Tell us which process needs an application.
Online scheduling is not available yet.
Your enquiry
This comes with you to the contact form. The link only carries the service and the model.
- Service
- Full-stack product development
- Model
- Block of hoursRemove or change the model