InPerceptic | Software Architecture Consulting

Adam Walkowski

Freelance Software Architect

About Me

Hi, I'm Adam.

I founded InPerceptic to help transforming digital products into fast-growing systems. I've spent the last 15+ years helping teams build software that actually works — systems that scale, integrate cleanly, and don't collapse under their own complexity.

I got into architecture because I kept seeing the same problems: decisions made in meetings and lost by implementation time, documentation that nobody reads, teams talking past each other. I wanted to fix that.

These days, I work with engineering teams as a partner — not a consultant who drops a PDF and disappears. I help you design systems, write specs that actually get used, and create documentation your team will thank you for.

I also have a background in visual communication and digital media, which shapes how I think about documentation — every diagram should tell a story, not just fill a slide.

How I Work

Most architecture work dies in Enterprise Architect, Confluence or ADR documents. I use something called Specification-Driven Development — architecture as code, not documents:

Specifications as Code — machine-readable, not prose
Generated Artifacts — diagrams derived from source of truth
Executable Contracts — API boundaries validated automatically
Living Documentation — always current, never stale

LinkedIn Profile Let's Talk

How I Can Help

Different Starting Points, Same Goal

Architecture that works. Let's find what fits your situation — whether you need a fresh perspective, a full design sprint, or someone to tell you what's really under the hood.

SVC11-2 weeks

Architecture Diagnostic

Not sure where you stand? I'll take a clear-eyed look at your architecture — the good, the risky, and the 'we'll fix it later' parts.

What You'll Get

Honest assessment of your current architecture
Interactive map of your system (yes, you can explore it)
Clear list of risks and technical debt
Prioritized recommendations — what to fix first
Executive summary if you need to share upward

Good fit if: You're unsure about your architecture's health, preparing for a big decision, or need a second opinion.

SVC22-4 weeks

Architecture Sprint

Building something new? Modernizing something old? Let's design it right from the start with specs that actually get used.

What You'll Get

Architecture blueprint (machine-readable, not just PDFs)
Interactive context map showing bounded contexts
Component and integration specifications
Generated diagrams (C4, sequence, flow) — always up-to-date
Architecture Decision Records — so future-you knows why

Good fit if: You're starting a new product, modernizing legacy systems, or need clear specs before handing off to vendors.

SVC31-3 weeks

Technical Due Diligence

Making a big investment? You need to know what's really under the hood. I'll give you the real picture, not just a report full of caveats.

What You'll Get

Comprehensive due diligence report
Risk assessment matrix (visual, not buried in text)
Technical debt quantification
Scalability analysis — can this thing grow?
Board-ready presentation

Good fit if: You're evaluating an acquisition, preparing for due diligence, or need to communicate tech reality to investors.

SVC41-2 days

SDD Training Workshop

Want your team to adopt this approach? I'll teach them hands-on — how to create and maintain executable specifications, how to think in bounded contexts, how to make architecture visible.

What You'll Get

Hands-on workshop (not death by slides)
Template specifications your team can reuse
Example diagrams and visualizations
Reference materials for after the workshop
Follow-up Q&A session

Good fit if: Your team wants to adopt specification-driven development, or you want to level up your architecture practices.

Interested? Let's talk

Not sure which fits? That's what the conversation is for.

Let's Talk

I'm proud to have worked with these amazing people

"Adam is highly passionate about architectural design and obtaining deep technical understanding of the domain at hand. He has a critical eye towards these aspects and towards our current standing and he brings to the table potent avenues that he has researched that could further improve the project."

Erlend Wollan

Software Architect at Axbit AS

"Thanks to Adam's ability to consider the project as a whole and in the long term, we knew how to prioritize issues to increase the project's potential. Adam is a person who not only performs entrusted tasks on time and precisely, but also goes out with his own initiative and takes over the responsibility."

Mateusz Perowicz

Product Manager at Klub Jagielloński

"Adam helped us to start up two new projects and perform their architectural design. His technical input in organizing backend services provides the team with a structured yet simple design approach for technical solutions. Adam provides also good practices from frontend frameworks usage."

Paweł Śledziński

CEO of Perfect One Software

Insights

Architecture Thinking

Thoughts on software architecture, specification-driven development, and making complex systems understandable.

November 16, 2023

Article Title 2

A brief summary of the article 2.

Read article

November 11, 2023

Article Title 1

A brief summary of the article 1.

Read article

View All Articles

Common Questions

Frequently Asked Questions

How does an engagement typically work?

Every engagement starts with a discovery call - a conversation where I learn about your architecture challenges and context. If there's a fit, I'll propose a specific engagement scope with clear deliverables and timeline. Most engagements are project-based with defined scope: a Diagnostic assessment, an Architecture Sprint, or a Due Diligence review. You know what you're getting and when you'll get it.

How do you price your services?

Each engagement is scoped individually based on the complexity and context of your situation. After our discovery call, I'll provide a clear proposal with a fixed price for the defined scope. No hourly billing surprises. No scope creep. You know the investment upfront.

What's NOT included in your services?

I focus on architecture consulting - assessment, design, specifications, and visualization. I don't write production code for you (though specifications can drive implementation), provide emergency firefighting services for systems in crisis, or take on open-ended retainers without clear scope. If you need implementation help, I can recommend trusted partners or help you hire the right team.

What makes your approach different?

Most architecture consultants deliver PowerPoint decks and Word documents that get outdated immediately. I deliver executable specifications and interactive visualizations: specifications expressed as code, diagrams generated from source of truth, interactive maps you can explore, and contracts that can be validated automatically. The result: architecture artifacts that stay useful after I'm gone.

Can you help with an ongoing project, or only new designs?

Both. The Architecture Diagnostic is specifically designed for existing systems - understanding what you have, identifying risks, and planning improvements. For new systems or significant redesigns, the Architecture Sprint produces specifications for implementation. For investment decisions, the Technical Due Diligence provides independent assessment.

Do you work with teams remotely?

Yes. I'm based in Gdansk, Poland, and work with organizations across Central and Eastern Europe (CEE) and beyond. Most engagements are conducted remotely with a mix of asynchronous work and scheduled video calls. For intensive workshops or critical stakeholder alignment, on-site sessions can be arranged.

What industries do you work with?

I take a generalist approach - the methodology applies across industries. I've worked with organizations in biotechnology, finance, retail, technology, and more. That said, I particularly enjoy working with regulated industries (where documentation matters) and scaling tech companies (where architecture decisions compound).

Let's Talk

Got an architecture challenge? Just exploring options? Either way, I'd love to hear about it. Every project starts with a conversation.

No pitch. No pressure. Just a chat about your situation.