Analysis
Technology and stack review
Do you really need a rebuild? We review an application's structure and explain what to keep or change.
Analysis / Backend · Infrastructure
VAT-exempt under section 19 of the German VAT Act
Technical cost review
Hosting, tools and ongoing services: we organise up to ten cost items and include the work involved in a possible switch.
US$899.00
Total price · one-offVAT-exempt under section 19 of the German VAT Act
- One application and one hosting setup
- Up to ten recurring technical cost items
- Cost overview based on supplied documents
Your enquiry is non-binding. An order is created only when you accept our quotation .
Image 1 of 4
Service scope
Your result
- Cost overview showing sources of figures and assumptions used
- Comparison of selected alternatives including migration effort
Included
- One application and one hosting setup
- Up to ten recurring technical cost items
- Cost overview based on supplied documents
- Alternatives, switching effort and one written follow-up round
Excluded
- No migration or contract cancellation
- No savings guarantee
- No comprehensive financial or tax advice
Which projects does this service suit?
Suitable if …
- Your recurring tool and hosting costs are hard to keep track of.
- You want to consider switching costs and possible relief together.
Not suitable if …
- No reliable documents about costs or requirements are available.
- You expect blanket percentage savings without investigation.
What this covers
Are we paying too much for hosting and technical services?
Which services do you pay for each month, and which does the application still need? We organise your invoices and contracts. For a possible switch, we also consider required functions and migration.
The technology cost review organises up to ten recurring cost items for one application and hosting setup, based on documents you provide. It makes expenses and alternatives suitable for your actual requirements understandable.
Include switching effort before a cheaper plan looks attractive
Changing plans can require work on data, integrations and tests. We compare that effort with expenses eliminated and identify unresolved assumptions. The overview names the sources of figures. Migration, cancellation and signing contracts remain separate steps.
Does this sound familiar?
You don't have a complete overview
Hosting, database and other services are billed through different accounts. We assign the agreed invoice items to their tasks. Missing contracts or usage details remain open points.
A cheaper offer sounds tempting
Another hosting plan looks cheaper. Data transfer, required functions and the move itself also belong in the comparison. We place these items alongside recurring fees.
The application has changed
A service was purchased for a function that is no longer needed. Before cancelling, you must establish whether other application parts still use it. This dependency belongs in the cost overview.
How we approach it.
Assign invoices to technical tasks
We assign the agreed cost items to your application's technical services. We record how you use each service and which contract details are still missing. General business expenses are excluded.
Compare alternatives and switching effort
We compare recurring fees with the costs and work of switching. The overview states assumptions and unresolved verification steps. Changing providers, migration and cancellation are outside the package.
After handover
Assign each open item to someone who knows its usage and contract terms. Calculate a switch only when migration is included. Migration work can consume a lower monthly price's savings for a long time.
The check is not financial or tax advice and guarantees no savings. If the technical structure is the main unknown, the stack review may be useful first. An economic scenario can be explored in the potential calculator but must include real switching costs and your own assumptions.
Record a process we can reproduce: which page do you open, what do you click and what happens next? For operational questions, name the tools used and describe how changes reach the server.
Passwords, repository tokens and production data must not be included in the enquiry. We agree required documents and suitable access separately.
Terms used in this service
What does that mean?
- Recurring costs
- Regular expenses for operation, such as hosting fees. For comparison, these are listed separately from one-off switching costs.
- Switching effort
- The work involved in moving to another solution, including data migration, integration changes, retesting and team familiarisation.
- Cost item
- An expense assigned to a technical task. Several invoice lines may belong to one service; we clarify this assignment before the review.
Before your enquiry
Questions about the offer.
What is included, what do you need and what happens after your enquiry?
The process in detail →Do you cancel unnecessary services?
No. The result is a cost overview with options and switching effort. Cancellations and contract changes remain separate decisions. Your team can first check dependencies and contract periods.
Do you need my complete accounts?
No. We need the agreed technical cost items and relevant documents. Unrelated business or customer data is not required. We agree the precise scope before transfer.
Can you guarantee a specific saving in advance?
No. The review may show that the existing setup suits the requirements. It should enable a reliable comparison, not justify a predetermined savings figure.
Do ten items mean ten separate invoices?
This means up to ten recurring technical cost items defined in advance. We agree beforehand how repeated invoices or related services are classified. The limit cannot be bypassed by arbitrarily grouping an entire infrastructure together.
Can the review include cloud and hosting costs?
Yes, where they belong to the agreed application, hosting setup and defined items. Name the services in your enquiry. The scope does not automatically include every account, project or contract in an organisation.
Will a cheaper alternative be set up technically?
No. Describing an alternative and its switching effort is not a migration. An actual change requires its own reviewed scope and appropriate operational approvals. The analysis does not alter existing operations.
When does work begin?
The work window is confirmed in writing before commissioning. Work starts once all required materials are available.
Which access is needed?
A sanitised cost overview without credentials or unnecessary personal data Information about usage, requirements and billing intervals A specific question about operating costs or switching options Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
What happens after handover?
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.
Read more on this topic
AI prototype before launch: what a focused check can do
What must work before the first use? Review a user journey including failure cases and record which technical questions remain afterwards.
Read the guide ↗Related services
These may fit too.
Analysis
MVP launch check
Your prototype works in the demo. We review one user journey and identify what is missing before your next launch.