From October 2026 I am opening capacity for one new long-term B2B engagement.

Solution architect · Fractional CTO · Business-critical modernisation

When the business depends on the system, code alone is not enough.

I help medium-sized and enterprise companies decide what to build, replace legacy systems without disrupting operations, and move AI from pilot to production. For more than 15 years I have been designing business-critical architecture, setting technical direction and leading delivery with client teams or with the fifteen-person Techcrowd team. If a project does not make technical or commercial sense, I will say so before development starts.

Book a 30-minute call See the workNo prep, no commitment. I reply by the next working day.

Miloš Novák — portrait photograph — **Miloš Novák**Solution Architect · Founder, Techcrowd

01 / When people call me

Most calls open with one of these sentences.

If one of them sounds familiar, I can tell you what can be done about it — and what can't.

„We need to replace a critical system, but we can't stop operations.“

It needs a target architecture, the change split into safe stages, and the old and new applications connected through clearly defined services and integration contracts during the transition.

„We have a vendor. But nobody on our side can judge what they're building.“

Invoices keep coming, deadlines keep slipping, and you have no one to verify whether any of it is sound.

„We've been trying AI for a year. It's still a demo.“

The pilot worked in a presentation. It never reached production, because nobody solved data, security and cost.

„One person holds the whole system together. And he just resigned.“

Nothing is written down, there is no documentation, and nobody knows what happens after he leaves.

02 / Services

Four things you can hire me for.

Each one is defined by its deliverable, not by the activity. You know up front what you get and what follows.

011–2 weeks

Technical audit and second opinion

I go through the architecture, the code, the integration points and the way delivery is run. I name the technical debt, the security and operational risks, and check whether the solution matches what the company actually needs.

Deliverable: An executive summary, risks ranked by priority, and a 30 / 60 / 90-day plan.
Who it's for: Companies that need an independent verdict on their own stack or on a vendor.
What follows: Either an architecture design, or handing the audit over to your team.

022–4 weeks

Architecture design

I translate business and operational needs into a target architecture, data model, integration boundaries and a realistic roadmap. For modernisation I also design the transition state in which the old and new systems can run safely side by side.

Deliverable: Target and transition architecture, an integration map, a staged roadmap, the key decisions and a cost estimate. Not an eighty-slide deck with no route to delivery.
Who it's for: Companies facing the decision of what to build and how.
What follows: Implementation through Techcrowd, or handover to your own vendor.

031–3 days / week

Fractional CTO

I take senior responsibility for technical direction: architectural decisions, standards, review of the critical parts, leading developers, dealing with vendors, and translating technical risk into terms the board can act on.

Deliverable: One accountable place for technical decisions, and someone who can defend them to the board, the development team and the vendor alike.
Who it's for: Companies where development works but the senior head is missing — and a full-time CTO doesn't make sense yet.
What follows: Ongoing collaboration, or hiring and handing over to an internal role.

042 phases

Taking AI from pilot to production

I turn one concrete business use case into a safe production service — search over documents, workflow automation, or an agent wired into internal systems. First I verify the benefit, the available data, permissions, compliance and running cost. Only then do we choose the model, RAG and infrastructure.

Deliverable: First a 2–3 week readiness check: use case, data, security and cost model. Only then implementation with a precisely defined scope.
Who it's for: Companies that want AI in production, not in marketing.
What follows: Extension to further processes, operations and monitoring.

I take the architecture and the key decisions personally. When a project needs full implementation, there is a team of roughly fifteen people at Techcrowd behind me.

03 / Results

Three numbers, not a list of technologies.

Systems that daily operations depend on — not a pilot, not a prototype.

years in production

Brink's · critical cash processing system

A system connecting operators, physical cash counters, logistics and downstream internal systems. Still being extended with further processes and integrations.

200+

estate agents in daily use

STING / BO! · web and mobile platform

A new application ecosystem built on existing data and delivered together with the client's development team.

32 → 420

hours a month over 18 months

STING · growth of the engagement

A thirteenfold increase in scope is evidence of long-term trust and of delivery landing, not of one-off work.

Client work and product lab →

04 / How I work

Architecture that survives change.

I am not an architect who delivers a diagram and walks away. I do my best work when a company needs to understand its operations, define a target architecture and split the change into stages that keep the business running throughout the transition.

Technical direction across an enterprise estate

Standards that hold across teams and applications.

For more than four years I worked as a frontend tech lead at Komerční banka. I was responsible for frontend direction across internal web applications, led the frontend guild and contributed to the development and adoption of a shared design system. I also worked on specialised initiatives including an internal chatbot and the selection and rollout of a standard charting library.

Frontend Tech Lead · Architectural standards · Design system · Guild leadership

Gradual modernisation of a critical operation

The old and the new world have to run side by side during migration.

At Brink's I lead analysis, solution architecture and technical direction across several connected operational systems. These include cash processing, a customer portal, secure partner integrations, billing and reporting, and the gradual replacement of dispatch and crew management applications. Because the operation cannot be switched off, we design transition architecture and shared services that let the legacy and target environments run safely side by side.

Solution architecture · Technical analysis · Integrations · Legacy migration

A new platform on top of existing data

A new ecosystem without losing the thread of current operations.

For the STING and BO! real-estate network we designed a new platform that had to reuse existing data, connect to legacy applications and be delivered in cooperation with the client's development team. The solution includes an application for estate agents, a mobile app, back office, a training platform, notifications and several supporting services. My role combined target architecture, integration boundaries and delivery leadership across teams.

Solution design · Microservices · Mobile + web · Multi-team delivery

Technologies change from project to project. My role remains the same: understand the business rules, find the system boundaries, expose the risks, define the target architecture and create a realistic path to production.

05 / How it works

Three steps before you spend anything.

Step 01

A thirty-minute call

You describe the situation. I tell you whether it's something I can help with — and if not, who to look for.

Step 02

A short assessment

I go through the system, the team and the context. You get a written summary of what I found, even if we go no further.

Step 03

The decision

Either we agree on one of the four things above, or you take the recommendation elsewhere. Both are fine.

06 / Who I'm not for

Better said up front.

01
Hourly rates and "how much does the cheaper one charge". I work towards an outcome, not billable hours.
02
WordPress and Wix sites, template presentations. Not my domain, and you'd find someone cheaper.
03
"A quick AI chatbot with no connection to our data." A demo detached from the system moves nothing.

07 / References

What the people I've worked with say.

„We have been working together for over a year with positive results. The main strength is a fast response and the search for new options. The company is open to developing and delivering customised solutions.“
Róbert KuchárCIO

„Requirements were handled and continuously discussed throughout development so that everything matched our needs. We use the system daily, we are very satisfied and we recommend the company.“
Ing. Jaroslav Macháčeklogistics manager · ABC pack

„I appreciate Miloš's consistent, systematic and at the same time innovative approach to solving problems. I value him as a leader who can bring a team together by using their strengths.“
Ing. Oldřich Šmíddeveloper, owner · ITSmid s.r.o.

„They built us a custom booking system for blood donors in a very short time. I appreciate their flexibility and the speed of their service response.“
Mgr. Jan Nováktransfusion preparations · Čáslav City Hospital

08 / Contact

In 30 minutes we'll know whether the problem is technical, organisational — or whether the project makes sense at all.

Describe the system, the team and the decision you are facing. If I'm not the right person, I'll say so and point you to the next step.

Book 30 minutesBook a 30-minute call Send an emailnovak@techcrowd.cz Call+420 728 826 186

I reply by the next working day at the latest.

B2B engagements · Remote-first · Czechia and the EU · Onsite as the phase requires