A written deliverable
A document you can hand to a third party, rather than a summary delivered on a call.
TECHNOLOGY CONSULTING · AUDITS
We review a system, a proposal or an offer from a supplier. You receive a written opinion that says what is sound, where the risk sits, and what to do next.

What you get
01
We walk the design, or the system as it actually runs, and name what holds up and where the risk sits. Every call comes with the reasoning behind it.
02
Where the technical debt sits, and which parts are cheaper to rewrite than to save. Your vendor can read it and argue with it.
03
A decision matrix and a pilot plan, so you are not buying from a slide deck.
04
What you are missing for VAT, archiving and e-invoicing, ordered by what is actually on fire.


Pricing
First step
A good fit when: You first need to check whether the problem is a fit for us.
We work out whether we can help. It is not a sales pitch.
1 200 € + VAT
Timeline: 3 days
What you get
1 500 € + VAT
Timeline: 4 days
What you get
2 400 € + VAT
Timeline: 7 days
What you get
Help as needed
A good fit when: You have one specific question without a fixed deliverable.
One-off questions, follow-ups and the small decisions in between.
BRIEF FOR PRICING
Email the file to rise@rise.sk or paste a share link into the form.
Who this is for
You need an expert view before a purchase or a refactor, or before choosing a vendor.
The project has risk in scope, team, architecture, or operations.
The internal team needs an experienced partner for technical decisions.
Proof · Owned digital product
MojaFirma links documents to invoices and tasks, showing their status and sending uncertain results to a person for review.

Before commissioning the work
Questions to ask about scope, pricing and responsibility for the project
Before you commit
How it runs
We work out whether we can help. It is not a sales pitch. We clearly state what we can assess.
A document you can hand to a third party, rather than a summary delivered on a call.
The person answering has actually written this kind of system.
A consultation is not a ticket into a project. The output is yours even if you pick someone else.
Decision brief · Technology consulting and audits
An important technical decision has no independent evidence and no clear risks. Often no owner either.
First paid step
A review and a written report, walked through with you.
What we need from the client
Email the file to rise@rise.sk or paste a share link into the form.
How to prepare a project briefWhen it is not the right move
You only need junior capacity without leadership or accountability.
The decision is already politically closed and technical audit will not change anything.
Questions
We join the leadership team for 2 to 8 hours a week as needed. That time goes on architecture, suppliers, hiring and whatever technical decision is open.
The price for a standard code or architecture audit is in the table above. A larger system needs its scope agreed first, and either way you leave with a written opinion.
Yes. The first conversation is free. You can then order a one-off audit or only the hours you currently need.