Consulting

Most consulting engagements stop at engineering recommendations. Ours start there and reach into business strategy, organization, and architecture. The dual-founder structure (business and technical) means strategy and engineering depth sit in the same conversation, the same proposal, and the same delivery.

Where our consulting reaches

Public-tender response

International public procurement is a discipline of its own. We have hands-on experience navigating EU and beyond — RFP and RFI analysis, bid architecture, partner consortium design, compliant response construction, and the often-overlooked documentation craft that decides whether a bid actually passes formal review.

Typical engagements:

• Reading and decoding a tender’s actual requirements (versus what the text superficially says).
• Designing a response architecture before writing — what wins, what loses, where to spend the budget.
• Building or coaching a consortium response with multiple partners.
• Reviewing a draft response against the formal scoring grid before submission.

Organizational rebuild

When an organization grows out of its old structure, the symptoms show up first in IT: too many systems, too much shadow work, too many handoffs that lose information. The cure is not “more agile training.” It is enterprise architecture and organizational design done with discipline.

Our reference frameworks:

• TOGAF — the de-facto standard for enterprise-architecture governance. We treat it as a toolbox, not a religion.
• Kotusev’s Best Practice Architecture — a pragmatic alternative to TOGAF’s heavier process, grounded in what real large organizations actually do.

Typical engagements:

• Defining current-state and target-state architecture at the enterprise level.
• Designing the architecture-governance function (board, reviews, escalation paths).
• Rebuilding domain boundaries between teams to reduce cross-team friction.
• Drafting a realistic transition roadmap with sequenced milestones.

Architecture & Security team building

The most expensive mistake is hiring senior architects and security engineers without a clear role design. We help build competent in-house architecture and security teams that can run things long-term.

Typical engagements:

• Drafting role profiles (Enterprise Architect, Solution Architect, Security Architect, Penetration Tester, GRC) that reflect the actual work, not LinkedIn templates.
• Designing onboarding paths and competence ladders.
• Reviewing candidates with you during hiring rounds.
• Coaching the first 90 days of a new hire so the investment actually lands.

Holistic engagements

End-to-end engagements that align business strategy, processes, and technology. The CEO/CIO split inside Pronix means the business framing and the technical depth do not get handed off between silos.

Typical engagements:

• A new product or service line where strategy, organization, and technology need to land together.
• A merger or carve-out where two operating models need to be reconciled.
• A digital-transformation programme that has stalled on org-chart disputes.

Business-process modelling

BPMN-grade process design. Turning ambiguous workflows into documented, optimizable systems. The starting point for any serious automation effort — without proper process design, automation only encodes existing inefficiencies faster.

Security architecture review (independent)

An external, independent perspective on your security architecture. Concrete recommendations, prioritized by impact, documented in a form you can hand to your board or auditor.

Typical scope:

• Default-deny posture, segmentation, blast-radius analysis.
• Identity boundaries, key custody, certificate lifecycle.
• Vendor-trust assumptions, supply-chain exposure.
• AI-assisted development controls (review discipline, audit trails).

When this fits

• You are preparing a major bid and want senior input on response strategy before you commit budget to writing.
• Your organization has grown out of its structure and you need a credible roadmap to a new one.
• You are about to hire your first (or your tenth) architect or security engineer and want the role design and onboarding to actually work.
• You have a strategic decision in front of you that spans business, organization, and technology, and you do not want it to get fragmented across three different advisors.
• Your security architecture has not been reviewed by an outside set of eyes in years.

What you get

• Working sessions with the people actually making the decisions — CEO/CIO/CISO, architects, engineering leads, procurement, HR where relevant. No watered-down status meetings.
• A written report. Findings, prioritized recommendations, trade-offs spelled out, alternatives considered. Something you can hand to a board, an auditor, or a successor.
• Concrete next steps. Not “you should consider…” but “do this first, then this, then this — and here is why.”

What sets this apart

• Strategy and engineering in the same head. Most consultancies have a business team and a tech team that meet twice. We do not. The two founders span both worlds and collaborate on the same deliverable.
• Decades of combined experience. More than 50 years across automation, digitization, security, organizational change, and enterprise architecture — applied to real engagements, not PowerPoint frameworks.
• No proprietary lock-in. We use TOGAF, Kotusev, BPMN, and the open-source ecosystem because they are auditable and vendor-neutral. We do not sell you back into a vendor we have a referral deal with.

Engagement shape

• Typical duration: 1 week to 3 months, depending on scope.
• Typical deliverable: a written report (10–80 pages), plus working sessions before, during, and after.
• Pricing: fixed-fee per engagement after a free scoping conversation. No surprises, no time-and-materials drift.

Reach out and we will scope a first conversation.