Service6 of 6
Consulting and architecture
We help you decide with the facts in hand. A technical diagnosis, a roadmap and an estimate in writing, before you commit budget.
- Category
- Consulting and architectureVerified
- Detailed capabilities
- Pending verification
- Engagement models
- Fixed-scope project
- Block of hours
- Handover record
- Repository · Documentation · Access · Infrastructure in your name
One decision and its alternatives
Illustrative diagram. It does not represent any client’s architecture.
How do we organize the code of a new application?
- Monolith
- Modular monolith
- Separate services
| Criterion | Monolith | Modular monolith | Separate services |
|---|---|---|---|
| Cost of changing one part | High | Medium | Low |
| Operational load | Low | Low | High |
| Demand on the team | Low | Medium | High |
| Time to the first release | Low | Medium | High |
Every state
Monolith
One application and one deployment. The fastest way to start.
- Cost of changing one part: High
- With no internal boundaries, a change touches parts you did not expect.
- Operational load: Low
- One deployment, one database, one place to look.
- Demand on the team: Low
- Any web team can maintain it.
- Time to the first release: Low
- Nothing to coordinate between pieces.
- Suits
- The product is still finding its shape and the team is small.
- Revisit if
- Unrelated changes keep colliding in the same file.
- Nobody dares touch one part for fear of breaking another.
Modular monolith
One deployment with modules that only talk through declared interfaces.
- Cost of changing one part: Medium
- Each module changes inside without touching the others.
- Operational load: Low
- It runs like a monolith.
- Demand on the team: Medium
- The boundaries between modules have to be respected; tests check them.
- Time to the first release: Medium
- Defining the modules takes some design up front.
- Suits
- The domain already has clear parts and it helps to be able to split them later.
- Revisit if
- One module needs to scale or ship at a different pace from the rest.
- Different teams block each other on the same deployment.
Separate services
Each part deploys and scales on its own, with its own database.
- Cost of changing one part: Low
- Each service changes and ships alone, as long as its contract does not change.
- Operational load: High
- Several deployments, a network between services and distributed monitoring.
- Demand on the team: High
- It calls for experience with distributed systems and operations.
- Time to the first release: High
- Contracts, infrastructure and pipelines before the first feature.
- Suits
- There are independent teams and parts with very different load needs.
- Revisit if
- Coordination between services costs more than they gain apart.
- Almost every change touches several services at once.
Related scope: Technical diagnosisRoadmapsTechnical documentation
What it solves
Common situations, not client cases.
- P-01
You have to approve a technical budget without knowing whether the proposal makes sense.
What changesA diagnosis of the options and their consequences, in writing.
- P-02
You want to change vendors and don’t know what to ask for so nothing gets lost in the move.
What changesA transition plan: what is handed over, in what order and how it is checked.
- P-03
Your project is stuck because nobody has defined what is in and what is out.
What changesA defined scope and an estimate you can use to request proposals, from us or from others.
What’s included and what isn’t
Included
The current state of your systems, their risks and their constraints, explained for those who decide.
What to do, in what order and why, with the dependencies between steps.
What you need to receive from the outgoing vendor and how to check it is complete.
A system’s architecture, decisions and workings, written for whoever will maintain it.
What is in, what is out and how much effort it takes, before you contract the build.
Not included
Proposal pending approval- EX-01
Legal or tax advice
Not offered. Your own advisers review those aspects.
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 Consulting and architecture
- EN-05
Diagnosis document
The current state, the risks and the options, in writing.
Passes to you
- EN-06
Roadmap
The recommended steps, their order and what depends on each one.
Passes to you
- EN-07
Estimate
The defined scope and the estimated effort, ready for requesting proposals.
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.
Consulting is contracted as a fixed-scope engagement, such as a diagnosis, or as a block of hours for occasional questions. The retainer is for platforms in production.
| Criterion | AFixed-scope projectSelectedRemove: Fixed-scope project | BBlock of hoursEnquire with this model: Block of hours |
|---|---|---|
| When it applies | When you need a diagnosis, a roadmap or an estimate with a clear goal. | When questions come up now and then: reviewing a proposal, backing a decision. |
| How it works | We agree what is analysed, with what information, at which milestones and at what price. | Prepaid hours used question by question, with a log of what was done. |
| Deliverables | Diagnosis, roadmap or estimate, as set in the proposal, and a handover record. | Hours log and the documentation for each consultation. |
| Contract considerations | The price is set in the proposal. Scope changes are reviewed in writing. | How long the hours stay valid, and on what terms, per the contract. |
- A
Fixed-scope project
- When it applies
- When you need a diagnosis, a roadmap or an estimate with a clear goal.
- How it works
- We agree what is analysed, with what information, at which milestones and at what price.
- Deliverables
- Diagnosis, roadmap or estimate, as set in the proposal, and a handover record.
- Contract considerations
- The price is set in the proposal. Scope changes are reviewed in writing.
- B
Block of hours
- When it applies
- When questions come up now and then: reviewing a proposal, backing a decision.
- How it works
- Prepaid hours used question by question, with a log of what was done.
- Deliverables
- Hours log and the documentation for each consultation.
- 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, which we agree with you before starting. The diagnosis is paid. If you then go ahead with the project, its fee is credited against the proposal.
The documents agreed in the proposal: diagnosis, roadmap or estimate, in a format your team can keep and edit.
Yes. We define what you need to receive from the outgoing vendor (code, documentation, access and infrastructure) and how to check it is complete.
Yes. We can sign a confidentiality agreement and intellectual property agreements covering the deliverables.
We issue CFDI 4.0 electronic invoices, the Mexican standard.
Your enquiry
This comes with you to the contact form. The link only carries the service and the model.
- Service
- Consulting and architecture
- Model
- Fixed-scope projectRemove or change the model