Insights
Field notes &
working papers.
Analysis, frameworks, and field guides from the Protabyte consulting practice. Written for engineering leaders, CTOs, and technical decision-makers.
Field notes
AI-enabled engineering for domain-heavy platforms
AI tooling is genuinely useful in software modernization — but not in the ways most people assume. The value is in compressing the scale-dependent parts of the work: codebase archaeology, test scaffolding, documentation drafting. The judgment-dependent parts still require engineers who understand the domain.
Architecture note
Replacing isolated report pages with a unified analytical workspace
Government platforms often end up with 30+ isolated report pages, each with its own filter setup and no shared context. Consolidating them into a unified workspace requires more than a new frontend. It requires auditing session state, mapping stored procedure parameters sourced from it, and sequencing the migration so hidden dependencies do not surface mid-delivery.
Architecture note
What it takes to design an animal-first genetic testing platform from scratch
New-build platforms carry different architectural risk than modernization work. The constraint is not accumulated debt — it is making foundational decisions that will govern how the platform grows for years. This note covers the design principles behind a new animal genetic testing LIMS built from first principles.
Case study + insight
Turning Operational Data Into a Usable Growth System
When a platform has rich operational data but a CRM that cannot represent the relationships that actually drive growth, the gap shows up in every campaign. This article covers how Protabyte designed a custom HubSpot architecture to close that gap.
Field notes
When Tools Arrive Before the Plan: A Fractional CTO Perspective on Fixing a Stalled CRM Initiative
Growth-stage companies often adopt strong tools at exactly the right moment and still fail to get value from them. The cause is rarely the tool. This article examines a stalled HubSpot CRM initiative and the work required to bring it back on track.
Architecture note
Why internal admin workflows matter as much as customer-facing features
Every customer-facing capability creates a corresponding internal requirement. When those requirements are not designed for, they do not disappear. They become the responsibility of whoever is working the support queue that day.
Working paper
Modernizing public health systems without breaking the mission
Public health and federally-affiliated platforms face a distinct category of modernization challenge. The system cannot be rebuilt from scratch, the operational risk of disruption is high, and technical debt has accumulated across every layer. This working paper examines how to structure a modernization program that addresses security, runtime, dependencies, testing, CI/CD, and frontend concerns in a sequence that actually works.
Field guide
What a real modernization assessment looks like
Saying a platform needs modernization is easy. Knowing what that actually means across security posture, runtime model, dependency health, test coverage, CI/CD maturity, configuration architecture, and frontend stack — and knowing how to sequence the work — is the harder problem. This field guide walks through what a rigorous modernization assessment covers, using a public health software platform as the reference context.
Architecture note
When fulfillment should be decoupled from purchase
When a system requires full assignment at the moment of purchase, it is not just enforcing a workflow. It is making a structural bet that the business will always know everything it needs to know at checkout. That bet does not age well.
Architecture note
Why checkout friction often starts in backend architecture
When a purchase flow underperforms, the instinct is to look at the interface. In many cases the friction is not the result of poor design. It is backend architecture that was never built to support a clean purchase path.
Technical briefing
Designing intelligent document processing for regulated industries
How to architect a document AI pipeline that satisfies insurance, healthcare, and government audit requirements, without sacrificing accuracy, throughput, or operational flexibility.
Architecture note
Technical due diligence: what investors and acquirers actually want to see
A practitioner's perspective on what a rigorous technical due diligence assessment covers, what findings typically surface, and how to prepare a codebase and architecture for external review.
Field notes
When scientific software becomes operational infrastructure
Scientific and research-driven platforms often begin by solving domain problems effectively. Over time they become relied on as operational infrastructure. Modernization in these environments requires more than framework upgrades. It requires architecture discipline, clearer API boundaries, and careful handling of workflow dependencies.
Working paper
Why most AI pilots never reach production
A structured analysis of the five failure modes that keep AI proofs of concept from becoming production systems, and the architectural decisions that separate projects that ship from projects that stall.
Field notes
The strangler fig pattern in practice: a field guide for .NET platforms
A practical guide to incremental .NET platform modernization using the strangler fig pattern: where it works, where it breaks down, and how to sequence the migration to minimize production risk.
Working paper
When to hire a fractional CTO (and when not to)
The organizational situations where fractional technical leadership adds the most value, and the circumstances where a different engagement model would serve you better.
Technical briefing
How to run an architecture review that actually changes decisions
Most architecture reviews produce documents that nobody reads. This is how to structure a review that produces findings, drives decisions, and leaves the team with shared clarity on direction.
What we write about
Field Notes for Technical Leaders
New articles, frameworks, and working papers.
Delivered when published. No marketing cadence. Unsubscribe any time.
Looking for practical guidance now?
If you have a specific challenge you are working through and cannot wait for an article, a direct conversation is the fastest way to get useful input.