AI/ML
IOanyT Is Now ISO/IEC 42001 Certified
IOanyT Innovations is now certified to ISO/IEC 42001, the international standard for AI management systems. It covers how we build and govern AI ourselves.
• 3 min read
Read Article
All insights
Field notes from real work, regulation explained, and the economics of building and running systems. Browse by stream.
Featured
🔒 Security
IOanyT Is Now ISO 9001:2015 and ISO/IEC 27001:2022 Certified
IOanyT Innovations is now certified to ISO 9001:2015 and ISO/IEC 27001:2022 — independent confirmation of the quality and security management behind every delivery.
• 4 min read
Read Article
Research notes
The Rules Your Results Application Applies Keep Changing. Four Ways to Make a Change You Can Check, Weighed.
A results application is changed as courses and regulations change, and nobody can say what else moved. Four answers weighed, and what each one risks.
• 14 min read
Read Article
Research notes
A Replacement Plan Needs Stages Someone Can Check. Here Is the Benchmark We Would Set.
One completion date gives a board nothing to check. The benchmark we would set for a staged replacement plan, with evidence at each stage.
• 10 min read
Read Article
Research notes
How Much of What Care Rests On Have You Mapped? Four Measures, Now and Where They Should Be.
How many of the applications your care rests on are mapped, ranked by clinicians, written down or out of support? Four measures, where they start, the path.
• 12 min read
Read Article
Research notes
How Much of Your Own System Do You Hold? Four Measures, Now and Where They Should Be.
When a supplier built your hospital's system, it holds the only description. Four measures of what you hold, where they start and should be, and the path.
• 12 min read
Read Article
Research notes
There Is No Newer Version to Move To. A Software Firm Does Not Have to Stop Selling to Leave.
When a product's technology has no supported version left: what buyers' and makers' rules now ask, four ways out, weighed, and the one we would recommend.
• 13 min read
Read Article
Research notes
Your Product Still Has a Data Store From Its First Version, and It Is on Nobody's List. What the Firm Lacks Is a List Taken From the Code.
A product that has run for years keeps data in stores nobody remembers. What we found, why memory falls short, four ways forward and the benchmark we set.
• 13 min read
Read Article
Research notes
Operators Can Count the Accounts They Marked. What Nobody Can Count Is Who Was Never Asked.
What an operator's records can say about customers who depend on the old phone line: a regulator's decision, why old systems stay, and our benchmark.
• 14 min read
Read Article
Research notes
The Product Moved to New Storage Three Years Ago, and the Old Store Is Still Running. A Benchmark for Every Old Store.
When a product moves to new storage or is rebuilt, the old store is often left running with no decision on it. The options, and the benchmark we would set.
• 12 min read
Read Article
Research notes
Your Policy Says the Record Is Deleted, and Nobody Has Read What the Code Does. Four Ways to Find Out, Weighed.
A firm's policy says a record is deleted; whether its code does is another question. What that gap costs, four ways to find out, and what we recommend.
• 12 min read
Read Article
Research notes
Your Results Rest on Rules Written Down Only Inside the Application. Here Is What the Public Record Shows.
The rules a results application applies are often written down nowhere else. What the public record shows, the options weighed, and the benchmark we would set.
• 14 min read
Read Article
Research notes
A New Application Is Not the Same as Every Rule Carried Across. Where Your Records Are Now, and Where They Should Be.
Before an operator replaces an old application, every rule it holds for customers who depend on the line should be listed. Our benchmark, as targets.
• 14 min read
Read Article
Research notes
Recorded in One System Is Not Known in the Next. Four Ways to Deal With a Status That Gets Lost, Weighed.
An operator records that a customer depends on the phone line, yet the order screen never shows it. Why that status gets lost, and four ways forward, weighed.
• 14 min read
Read Article
Research notes
The Application Your Wards Rely On Most Is Often the Oldest. Four Ways to Answer That, Weighed.
The application a hospital's wards rely on most is often its oldest. Four ways to answer it, from patching in place to staged replacement, and our advice.
• 12 min read
Read Article
Research notes
The Regulator Can Now Stop a Lender's Growth Over Its IT. Most Boards Hear It Last.
We reviewed the RBI's published action over IT failings: what a restriction holds back, four ways to find out where a system stands, and our benchmark.
• 10 min read
Read Article
Research notes
The Regulator Named the Areas in Public. The Record Behind Them Can Be Ready First.
The RBI named the IT areas in public when it restricted a bank. What a record built from the system opens up, four options weighed, and our recommendation.
• 10 min read
Read Article
Research notes
One Step in Results Processing Takes Most of the Time. Here Is the Benchmark We Would Set.
Marks merged by hand and an old program that stops: one step of results work often takes most of the time. The benchmark we would set, and the path to it.
• 14 min read
Read Article
Research notes
When a Supplier's System Stops, a Hospital Learns What Depended on It. That Can Be Known Beforehand.
A hospital cannot stop a supplier's system failing. It can know beforehand what would stop. What the public record shows, three ways to map it, our benchmark.
• 12 min read
Read Article
Research notes
When Hospital Systems Stop, Care Stops. Which Ones It Rests On Can Be Known Beforehand.
No one can promise a hospital its systems will stay up. It can know which applications care rests on. What the record shows, three options, our benchmark.
• 13 min read
Read Article
Research notes
While One Large Figure Waits for Approval, New Options Wait Too. Four Ways to Replace, Weighed.
A replacement arrives as one figure nobody can judge, and new options such as a second intake wait. Four ways to replace, weighed, and what each risks.
• 13 min read
Read Article
Research notes
Your Hospital Can Choose Another Supplier. Its Own System Often Cannot.
When a hospital's own system is wired to one supplier, it cannot switch, fall back or compare quotes. Four ways to answer that, weighed, and what we advise.
• 12 min read
Read Article
Research notes
A Supplier Runs Your System. Here Is the Benchmark for Overseeing It.
Supplier oversight often rests on the supplier's own evidence. The benchmark we would set for overseeing a critical supplier with your own evidence.
• 10 min read
Read Article
Research notes
A Change to a Pricing Rule Should Not Be a Leap of Faith. Here Is the Benchmark We Would Set.
In old programs one rule borrows from another, so a small change moves figures nobody meant to touch. Three ways to check a change, weighed, and our benchmark.
• 12 min read
Read Article
Research notes
A Deferred Replacement Is Still a Decision. Four Ways to Replace an Old System, Weighed.
Replacement estimates are revised because nobody read the old system first. We weigh four ways to replace it and say what waits while the decision is deferred.
• 12 min read
Read Article
Research notes
A Few Old Parts Hold the Whole Shop on an Old Version. Everything Else Waits With Them.
A few old parts hold an online shop on an out-of-support PHP version and database while add-ons, payments and couriers wait. Four ways to answer, weighed.
• 11 min read
Read Article
Research notes
A Firm That Does Not Hold Its Own Systems Cannot Plan a Move.
A retailer whose agency or former owner holds the code cannot get a second quote or plan a move unaided. What waits, four ways forward and a benchmark.
• 11 min read
Read Article
Research notes
A Hospital Has No Quiet Weekend. What the Record Says About Replacing Old Systems.
What the public record shows on replacing old hospital systems, why the decision keeps being put off, four ways forward and the benchmark we would set.
• 10 min read
Read Article
Research notes
A New Officer Takes Charge of Your System With Nothing to Read. Three Ways to Change That, Weighed.
Officers in charge of a public system change, and each inherits nothing to read. We weigh three ways to change that, and why we recommend a specification.
• 13 min read
Read Article
Research notes
A Price Agreed Years Ago Can Still Be Running. You Cannot Change a Rule You Have Never Read.
A manufacturer cannot change a cost or price rule, or move its ERP, without knowing the rules its programs apply. Four options and our benchmark.
• 12 min read
Read Article
Research notes
A Price History and a Ninety-Day Answer: What Waits on Retail Data Nobody Trusts.
New Indian rules on recent lowest prices and customer data requests both touch your data. What waits on data nobody trusts, four options and a benchmark.
• 11 min read
Read Article
Research notes
A Record Your Staff Open Before They Pick Up the Phone. Here Is the Benchmark We Would Set.
Most firms documented their old system once, and nobody opens it. The benchmark we would set for a record people use, and why we build no assistant.
• 12 min read
Read Article
Research notes
A Replacement You Can Pause Is One You Can Start. The Measures to Hold It To.
Percentage complete tells a board little. The benchmark we would set for a retail replacement: accepted modules, a price per stage, and a point to pause.
• 11 min read
Read Article
Research notes
A Technology You Can Hire For: The Benchmark for Moving an Old Application, Module by Module.
Good engineers decline work on a technology with no future. Three ways to move an old VB6 application, weighed, and the benchmark we would agree first.
• 12 min read
Read Article
Research notes
A Way Back Nobody Has Tried Is Not a Way Back. The Benchmark for a Release You Can Check.
Most teams release often and have never practised going back. The benchmark we would set for a tested release with a way back that has been tried.
• 13 min read
Read Article
Research notes
A Year After the Deal You Still Run Two of Everything. Here Is the Benchmark We Would Set.
A year after the deal, a group still runs two booking and two billing systems. The benchmark we would set, and a keep, replace or retire call for each system.
• 12 min read
Read Article
Research notes
About Half of PHP Websites Run a Version the PHP Project No Longer Fixes. The Reason Is Rarely Neglect.
Why so many websites run PHP and database versions with no security fixes, why every upgrade feels like a gamble, four ways forward and a benchmark.
• 12 min read
Read Article
Research notes
The Advert for a VB6 Developer Goes Unanswered. The Public Record Says It Is Not the Advert.
The advert for a VB6 developer goes unanswered because the market stopped making the skill. What we found, four ways to respond, and our benchmark.
• 12 min read
Read Article
Research notes
Everything Waits for "After the Replacement". Four Ways Forward, Weighed.
What customers and agents ask for is promised for after the replacement. What waits meanwhile, four ways forward weighed and a decision benchmark.
• 12 min read
Read Article
Research notes
AI Tools Wrote the Code Quickly. Nobody Was Given the Time to Read It.
AI tools wrote the code quickly and nobody read it. What we found, why the product gets harder to change, four ways forward and the benchmark we would set.
• 13 min read
Read Article
Research notes
Almost Right, but Not Quite. Four Ways to Handle Code Your AI Tools Wrote, Weighed.
Developers say AI-written code is often almost right, but not quite. What that costs a software firm, four ways to handle it weighed, and our recommendation.
• 13 min read
Read Article
Research notes
An Exception List That Only Grows Is Not a Plan. One That Shrinks Is.
On an unsupported server, a newly found flaw stays open. The benchmark we would set so a hospital's exception list shrinks, and which applications move first.
• 10 min read
Read Article
Research notes
An "Unsupported" Entry With No Date Is Not a Plan. A Shrinking List of Custom Code Is.
Quotes to move an online shop come in far apart. The benchmark we would set, and the path from a written scope to a move that can be priced and checked.
• 11 min read
Read Article
Research notes
An Upgrade Nobody Can Check Is a Gamble. A Shrinking List of Blocking Parts Is a Plan.
After a PHP or database upgrade under an online shop, "it seems fine" is often all anyone can say. The benchmark we would set, and how to check the upgrade.
• 11 min read
Read Article
Research notes
Applied, and Checked by Your Own Team. Four Ways to Deal With Security Fixes That Keep Waiting, Weighed.
Indian operators must report security incidents within hours. What that means when your applications carry fixes nobody dares apply, four options weighed.
• 13 min read
Read Article
Research notes
You Are Asked to Approve a Move Nobody Can Price. Where Your Replacement Plan Is Now, and Where It Should Be.
Bids to replace an operator's old billing applications come in far apart because nobody has read the system. The benchmark we would set, one stage at a time.
• 12 min read
Read Article
Research notes
Ask How a Product Cost Is Worked Out, and the Answer Is "Whatever the System Says". The Rules Are in Programs Nobody Has Read.
Costing and pricing rules sit unread in the reports and programs built around the ERP. What the public record shows, four ways to find them, and our benchmark.
• 12 min read
Read Article
Research notes
Ask Who Knows How the Dispatch System Works, and the Answer Is a Phone Number.
Many manufacturers must ask an outside partner or one person what their own system does. What the public record shows, four options, and our benchmark.
• 12 min read
Read Article
Research notes
Before Old Figures Are Carried Into a New System, Know Where They Were Made.
A new ERP or AI project starts with the figures the old system held. Three ways to prepare them, weighed, and the benchmark we would agree before the move.
• 12 min read
Read Article
Research notes
Every Billing Change Waits on a System Nobody Dares Touch. Four Ways Off the Old Applications, Weighed.
Billing complaints now run against set benchmarks while charging rules sit in apps nobody dares change. Four ways off the old applications, weighed.
• 13 min read
Read Article
Research notes
Changing Supplier Does Not Have to Rest on One Handover Day. Here Is the Benchmark We Would Set.
A supplier change pictured as one handover day keeps institutions stuck. Four ways to leave, weighed, and the benchmark we would agree before starting.
• 12 min read
Read Article
Research notes
Cleaned, and Wrong Again. Four Ways to Make Customer Records Stay Right, Weighed.
Indian operators now report billing complaint resolution and keep the records behind it. Four ways to keep customer records right after a clean-up.
• 13 min read
Read Article
Research notes
Data a New Tool Cannot Read Is Not Ready. Here Is the Benchmark for Ready.
A new reporting or AI tool sees only the years it can reach. The benchmark we would set before old hospital data goes to any new tool, and the path.
• 11 min read
Read Article
Research notes
Digital Health Now Asks for Records That Move. Many Hospital Systems Were Built to Keep Them.
Connected records and faster insurer claims need data to move between systems. What waits on an old hospital system, four ways forward and a benchmark.
• 11 min read
Read Article
Research notes
Eighteen Months In, With Nothing to Ship. The Benchmark We Would Set Before a Rewrite Starts.
A rewrite run as one job cannot be shipped or stopped until it ends. Four ways a board can govern one, and the benchmark we would set before it starts.
• 11 min read
Read Article
Research notes
An ERP Move Cannot Be Priced While Your Own Programs Beside It Are Unwritten.
An ERP move is hard to price because of the custom programs built beside the ERP. The benchmark we would agree first, and three ways to price the move, weighed.
• 12 min read
Read Article
Research notes
Every Change Waits on One Scarce Skill. Four Ways Out, Weighed.
When only one person can read an old VB6 application, every change waits on them. Four ways out, from hiring to conversion tools, weighed, and our benchmark.
• 12 min read
Read Article
Research notes
Every Document About Your System Goes Out of Date. Here Is the Benchmark We Would Set.
Documentation exercises go stale. We weigh four ways to keep a public system's record true and set out the benchmark: a record dated and traced to the code.
• 12 min read
Read Article
Research notes
Every Figure Your System Produces Should Trace to a Written Rule. Here Is the Benchmark We Would Set.
Changes to an old system are checked against memory because its rules were never written down. Four ways to check a change and the benchmark we set.
• 12 min read
Read Article
Research notes
Every New Service Waits Because the Budget Is Already Spent on the Old Ones. Four Ways to Make Room, Weighed.
Upkeep is provided for first, so new public services wait. We weigh four ways to make room and explain why we start with a keep-versus-replace cost comparison.
• 12 min read
Read Article
Research notes
Every Retail Replacement Story You Have Heard Is One Kind of Project. Yours Probably Is Not.
Every named retail replacement failure is a packaged ERP at a very large firm. What we found, why retailers wait, the options, and the benchmark we would set.
• 11 min read
Read Article
Research notes
Every Shop Has a Part That Gives Way First. Most Find Out Which on the Day.
Every shop has one part that gives way first under a rush, and most find out on the day. What the record shows, the options, and our benchmark.
• 11 min read
Read Article
Research notes
Every Year the Replacement Waits, the New Work Waits With It.
Hospitals defer replacing old systems as estimates grow, while connected records and faster claims wait. Four options weighed and a decision benchmark.
• 11 min read
Read Article
Research notes
Fixable Is Not the Same as Fixed. Where Your Applications Stand on Security Fixes Now, and Where They Should Be.
Some of an operator's applications run on software whose maker publishes no more fixes. Four ways to deal with one, and a benchmark that gives the count an end.
• 13 min read
Read Article
Research notes
Halfway Through a Rewrite, the Money Is Spent and Nothing Ships. Let the Old Product Be the Judge.
A rewrite judged only at the end has nothing to ship halfway through. What we found, four ways to run a rewrite, and why the old product should judge each part.
• 12 min read
Read Article
Research notes
Hospitals Keep Every Old Record. What Goes Missing Is What the Records Mean.
Old hospital records are kept, but their meaning goes out of reach. What the public record shows, why it happens, four ways forward and a benchmark.
• 11 min read
Read Article
Research notes
Hospitals Keep Unsupported Servers for One Reason. It Is Rarely the Server.
Hospitals keep unsupported servers because of the applications on them, not the machines. What the public record shows, four ways forward and our benchmark.
• 10 min read
Read Article
Research notes
How Many People Can Explain Your Hospital's System? Four Measures, Now and Where They Should Be.
When only one person can explain an old hospital system, every question waits. Four measures, where they start and where they should be, and the path.
• 10 min read
Read Article
Research notes
Invoices Now Have a Clock. Systems Joined by a Monthly File Run Behind It.
E-invoicing deadlines in India and Saudi Arabia set dates for invoices to reach a tax portal. What waits on unconnected systems, four options, a benchmark.
• 11 min read
Read Article
Research notes
"Is There a Web Version?" Has Been "On the Roadmap" for Years. What the Firm Lacks Is a List of Its Screens.
Prospects ask for a web version; it stays on the roadmap because nobody has listed what each screen does. What we found, four ways forward, our benchmark.
• 13 min read
Read Article
Research notes
"It Seems Fine" Is Not a Test. An Upgrade Your Own Engineers Can Check.
When a software firm upgrades the framework under its product, does it still behave as it did? What we found, the options, and the benchmark we would set.
• 10 min read
Read Article
Research notes
Known Flaws Stay Open for Years. What Nobody Writes Down Is What the Fix Would Break.
Known security flaws stay open at operators because nobody writes down what the fix would break. What the public record shows, four ways and our benchmark.
• 13 min read
Read Article
Research notes
Leaving Someone Else's Systems Is Not a Weekend. It Is a List, Then One Module at a Time.
Leaving systems held by someone else is not a weekend job. The benchmark we would set: list who holds what, then move one module at a time.
• 11 min read
Read Article
Research notes
Leaving Your Supplier Does Not Have to Be One Handover Day. Here Is the Benchmark We Would Set.
A change of supplier planned as one handover day is easy to defer. We weigh four ways to leave and set out the benchmark we would agree before any module moves.
• 12 min read
Read Article
Research notes
"Live" Is Not "In Use". Here Is the Benchmark We Would Set for a Replacement.
A new public system can be declared live and still go unused. We weigh four ways to decide a replacement is done and set out the benchmark we would agree.
• 11 min read
Read Article
Research notes
Many Firms Cannot Say Whose Name Is on Their Own Systems. They Find Out on the Worst Day.
Many retailers cannot say whose name is on their own systems until the worst day. What the public record shows, four ways to respond and a benchmark.
• 11 min read
Read Article
Research notes
New Digital-Health Work Is Waiting on Records Only an Old System Can Read.
An old system kept running only for its records holds back reporting, AI and connected records. Four ways to handle the archive and a benchmark.
• 11 min read
Read Article
Research notes
New Digital-Health Work Is Waiting on Servers Nobody Can Change.
Digital health records, incentives and faster insurer decisions all reach a hospital's oldest servers. What waits, four ways to answer, and our benchmark.
• 10 min read
Read Article
Research notes
New Offers Are Waiting on Shop Code Nobody Can Change.
New offers, campaigns and price-cut display rules all touch custom code in an old shop. What waits, four ways to answer it and a decision benchmark.
• 11 min read
Read Article
Research notes
The New Screens Look Better, and Your Oldest Customer Says the Totals Are Wrong. A Benchmark for Every Rebuilt Screen.
When a desktop product is rebuilt for the web, long-standing customers find the differences. The benchmark we would set to check every rebuilt screen.
• 12 min read
Read Article
Research notes
New Servers Are Not the Same as Off the Old Ones. Where Your Old Machines Are Now, and Where They Should Be.
New servers bought, old ones still on. The benchmark we would set so an operator counts the machines its own team has actually retired, not servers bought.
• 12 min read
Read Article
Research notes
A Newcomer's First Change Should Not Need a Senior Engineer's Memory. The Benchmark We Would Set.
On an old product, a newcomer's first change waits for a senior engineer's memory. What we found, the options, and the benchmark so it can be checked.
• 11 min read
Read Article
Research notes
Nobody Can Promise a Replacement Misses Nothing. A Benchmark Can Show It.
An old hospital system holds rules nobody wrote down. The benchmark to set before replacement, with each module checked and accepted by clinicians.
• 11 min read
Read Article
Research notes
Nobody Can Promise You a Peak Day. You Can Know Where It Will Be Decided.
Servers doubled, checkout still queues. The benchmark we would set before the next sale, what we would rebuild, and what we will not claim about peak volume.
• 12 min read
Read Article
Research notes
Nobody Can Say What a Database Upgrade Would Break. Here Is What the Public Record Shows.
Database support end dates are published; the list of what stands on each database is not. What we found at institutions, the options and our benchmark.
• 11 min read
Read Article
Research notes
Nobody Has Set Your System Beside the Rules It Was Built to Apply. Three Ways to Check, Weighed.
Public systems drift from the orders they apply and nobody compares the two. Three ways to check what a system calculates, and a new accuracy standard.
• 13 min read
Read Article
Research notes
Nobody Left to Ask. Four Ways to Deal With an Inherited System, Weighed.
After a deal, the new owner's team must change a system it did not write, with nobody left to ask. Four ways to deal with it, weighed, and our recommendation.
• 12 min read
Read Article
Research notes
Every Operator Agrees the Old Billing Applications Must Go. What We Found Is Why Nobody Names the Date.
Every operator agrees old billing applications must go. What the public record shows on why nobody names the date, four ways forward and a benchmark.
• 13 min read
Read Article
Research notes
Old Health Applications Lack the Basic Locks. The Reason Is Inside the Application.
Old healthcare systems lack basic security controls, and the obstacle is usually the application itself. What we found, four ways forward and our benchmark.
• 11 min read
Read Article
Research notes
Old Servers Outlive Their End Dates for One Reason. Nobody Has Listed What Stands on Them.
Manufacturers keep servers, databases and ERP versions past their end dates while nobody lists what stands on them. What we found, four ways and our benchmark.
• 12 min read
Read Article
Research notes
One Old Application Can Keep a Whole Server Past Its End Date. It Can Be Rebuilt by Itself.
A manufacturer cannot retire an old server, or price its ERP move, while nobody lists what stands on it. Four ways forward, weighed, and our recommendation.
• 12 min read
Read Article
Research notes
One Old Application Can Keep Every Other on an Unsupported Database. Four Ways Out, Weighed.
A college database often stays unsupported because one old application will not run on a newer version. Four ways out, what each risks, what waits.
• 13 min read
Read Article
Research notes
One Old Program Can Keep a Server Switched On. Extended Support Is One Answer of Four.
A firm moves to new servers and keeps the old one on for one or two programs. Paid support, a move as it is, a packaged product or a rebuild, weighed.
• 12 min read
Read Article
Research notes
One Person Knows How the Product Works. What the Firm Lacks Is a Record That Person Has Checked.
One person knows how the product works; the firm lacks a record that person has checked. What the public record shows, four ways forward and our benchmark.
• 12 min read
Read Article
Research notes
One Price at Renewal, and Nothing to Compare. Four Ways to Deal With a Vendor You Depend On, Weighed.
With no written record of what your applications exchange with a vendor's product, there is no comparable second quote. Four ways forward, weighed.
• 13 min read
Read Article
Research notes
One Way In. A Benchmark for How Changes Reach Your Live Product.
When a person or an AI tool can change the live product directly, nothing checks the change. The benchmark we would set so every change goes the same way in.
• 13 min read
Read Article
Research notes
Online Shops Stay on Unsupported Versions for One Reason. It Is Rarely the Platform.
Online shops stay on platform versions their maker no longer fixes. What the public record shows, why the shops stay, four ways forward and our benchmark.
• 11 min read
Read Article
Research notes
Only One Firm Can Quote for Changes to Your System. A Record You Hold Changes That.
When only the partner who built a system can describe it, only that partner can quote for changes. Four ways out, our recommendation and a benchmark.
• 12 min read
Read Article
Research notes
Only One Firm Can Quote for Your System. A Second Quote Starts With a Document.
When only your vendor can change your system, it sets price and timetable. What that costs, what a second quote opens, four options and a benchmark.
• 9 min read
Read Article
Research notes
Only One Person Can Put the Product Live. The Benchmark for a Release Anyone Can Make.
At many software firms a release reaches customers only when one person runs the steps from their own computer. The options, and the benchmark we would set.
• 11 min read
Read Article
Research notes
Only the Supplier Can Say What Your System Does. Four Ways Forward at the End Date, Weighed.
No tender can be written without a description of the system. Four ways forward at the end date, what each risks, and why getting the code comes first.
• 12 min read
Read Article
Research notes
Only Your Vendor Understands the System. Here Is What the Public Record Shows.
What the public record shows on lenders that depend on one vendor or shared provider, what it leaves out, the options, and the benchmark we would set.
• 10 min read
Read Article
Research notes
Operators Clean Their Customer Records Every Year. What Nobody Has Found Is Where the Records Go Wrong.
Operators clean customer records every year, yet the errors return. What the public record shows, why clean-ups do not last, and four ways forward.
• 12 min read
Read Article
Research notes
"Partially Implemented" Should Change Every Year. Here Is the Benchmark That Makes It.
Auditors and insurers ask if every system has basic controls. The benchmark that moves the answer for a health organisation's old systems each year.
• 11 min read
Read Article
Research notes
Your Planner Types the Same Figure Three Times. Four Ways to Stop It, Weighed.
Many manufacturers re-type the same figure across applications, ERP and plant records. What entering it once opens up, four options and our advice.
• 12 min read
Read Article
Research notes
Public Replacements Overrun, Fail at Go-Live or Go Unused. Here Is What the Public Record Shows.
Public replacements overrun, fail at go-live or go unused. What the public record shows, four ways to plan the switch, and the benchmark we would set.
• 12 min read
Read Article
Research notes
Ready to Move Is Not the Same as Known. Where Your Customer Records Are Now, and Where They Should Be.
Before a move to a new system, customer data is declared ready because counts match. The benchmark we would set so an operator knows where its records stand.
• 12 min read
Read Article
Research notes
Releasing Often Without Fear Is the Opportunity. Four Ways to Get There, Weighed.
A change can be reviewed, approved and still act on the wrong thing. What that costs a firm that cannot release without fear, and four ways to check a release.
• 13 min read
Read Article
Research notes
Consignments Now Meet Tax Clocks. Replacing Everything Is One Answer of Four.
E-way bill and e-invoice rules put time limits on documents re-typed between systems. What waits, and four ways to answer it beyond replacing everything.
• 13 min read
Read Article
Research notes
Rewrites Lose What Nobody Listed. The Old Product Is the List.
Rewrites lose what nobody listed. What we found, why specifying from memory leaves features out, four ways to specify a rewrite, and our benchmark.
• 12 min read
Read Article
Research notes
Sale Days Your Shop Cannot Hold. More Servers Are One Answer of Four.
More servers, a hosting move, a new shop, or a rebuild of the part that limits it. Four answers to a slow sale day, weighed, with our recommendation.
• 11 min read
Read Article
Research notes
A Software Firm That Rests on One Person Cannot Say Who Holds What. Four Ways Forward, Weighed.
Many outside services behind a software product were opened in one person's name. What a firm cannot do until it knows who holds what, four options.
• 13 min read
Read Article
Research notes
Software Firms Know Their Product Stands on Unsupported Technology. What They Lack Is a List.
Software firms know their product stands on an unsupported language or framework; what they lack is a list. What we found, four ways forward and our benchmark.
• 12 min read
Read Article
Research notes
Software Releases Are Checked Against the Faults Already Known. Customers Find the Rest.
Releases are checked against faults already known, and customers find the rest. What the public record shows, why it happens, and a benchmark.
• 12 min read
Read Article
Research notes
A Stock Count Corrects the Records. The Work That Waits Needs the Cause Fixed.
A full stock count fixes the records for a few weeks. The work that waits on untrusted figures, four ways to fix the cause, and our benchmark.
• 12 min read
Read Article
Research notes
The Changes Your Hospital Is Asked For Are Queuing Behind One Person.
Connected records and faster insurer decisions need changes to old hospital systems, and each waits on one person. Four ways out, weighed, and our advice.
• 11 min read
Read Article
Research notes
The Cost of Waiting Belongs Beside the Fear of Replacing. Four Ways Forward, Weighed.
Retailers price replacing an old system but leave the cost of keeping it blank. What waiting costs, a fixed date that will not wait, four options weighed.
• 11 min read
Read Article
Research notes
The End Dates Are Published. The List of What Runs on Each Old Server Is Not.
The end dates for server software are published; the list of what runs on each old server is not. What we found, four ways to answer and the benchmark we set.
• 13 min read
Read Article
Research notes
The Largest Line in Your Technology Budget Is the One Nobody Can Explain. Here Is What the Public Record Shows.
Where the total is known, upkeep takes most of a public IT budget, yet its parts rarely are. What we found, four ways to open the line, our benchmark.
• 12 min read
Read Article
Research notes
The Old System Outside Your Controls Is the Question You Cannot Answer Yes To.
Systems left behind by migrations and acquisitions sit outside a health organisation's security controls. What that costs, four ways forward and our benchmark.
• 11 min read
Read Article
Research notes
The Plan to Leave the Old Servers Has One Line for the Hard Part. Here Is the Benchmark We Would Set.
Plans to leave old servers describe the new setup and give the applications one line. The benchmark we would set before that line is signed, and who does what.
• 12 min read
Read Article
Research notes
The Regulator Now Looks at How You Change Your Systems. Most Old Systems Cannot Show a Change Was Safe.
Regulators now look at how firms change their systems, yet most old systems cannot show a change was safe. What we found, the options, our benchmark.
• 10 min read
Read Article
Research notes
The Rules for Your Fares Live in Code Two People Can Read. Here Is What the Public Record Shows.
Fare, schedule and cancellation rules often live in old code few can read. What the cross-sector record shows, the options, and the benchmark we would set.
• 12 min read
Read Article
Research notes
The Rules in Your System Were Decisions. The Business Can Make Them Again.
A rule nobody remembers is still applied to your customers. What deciding each rule again gives back, four ways to get there, and the benchmark we would set.
• 10 min read
Read Article
Research notes
The Scarce Skill in an Old Hospital System Is Reading It. That Can Be Done Once.
Many in-house hospital systems rest on the one person who built them. What the public record shows, three ways to keep what they know, and our benchmark.
• 11 min read
Read Article
Research notes
The Scarce Skill Is Reading the Old Code. Here Is the Benchmark for Needing It Less.
Every new engineer on an old lending system learns its code from an expert. The benchmark we would set so the reading is done once and kept.
• 10 min read
Read Article
Research notes
The Skills for Old Systems Are Running Out. The Knowledge Does Not Have To.
Old lending systems often rest on two or three people, and the skills behind them are scarce. What the public record shows, the options, and our benchmark.
• 10 min read
Read Article
Research notes
The Upgrade Is Your Team's to Do. Here Is the Benchmark We Would Set to Check It Against.
After a database upgrade most institutions can say the applications open, not that they give the same results. Four ways to check, and our benchmark.
• 12 min read
Read Article
Research notes
Two People Know How Your System Works. Four Ways to Stop Depending on Them, Weighed.
When one or two people know how the system works, a resignation is a business risk. Four ways to stop depending on them, weighed, and our recommendation.
• 12 min read
Read Article
Research notes
"We Documented It" Is Not the Same as Having the Rules. A Benchmark Shows the Difference.
A document of the application can still miss the rules held in the database, night jobs and spreadsheets. The benchmark we would set, and the path.
• 10 min read
Read Article
Research notes
When a Figure Is Questioned, "the System Shows It" Is Often the Only Answer. Here Is What the Public Record Shows.
When a figure is questioned, 'the system shows it' is often the only answer. What the public record shows, four ways to respond and our benchmark.
• 12 min read
Read Article
Research notes
When a Record Is Typed in Three Offices, Replacing Everything Is One Answer of Four.
A college with many separate systems is offered one cure: replace them all. Four answers weighed, what each risks, and what waits meanwhile.
• 13 min read
Read Article
Research notes
When the One Person Who Knows Is on Leave, the Firm Should Still Have an Answer.
When one person or one partner is the only one who knows a plant application, the firm waits. Four ways out, weighed, and the benchmark we would agree first.
• 12 min read
Read Article
Research notes
When the Supplier's Contract Comes Up, Nobody Can Write the Tender. Here Is What the Public Record Shows.
When a supplier's contract comes up, nobody can write the tender. What the public record shows on institutions tied to one supplier, and a benchmark.
• 12 min read
Read Article
Research notes
Your Systems Each Work. The Trouble Is Where a Consignment Crosses Between Them.
When booking, dispatch, tracking and billing each keep their own copy, errors start where data crosses. What we found, the options, our benchmark.
• 12 min read
Read Article
Research notes
"Who Said It Was Ready?" Is a Question to Answer Before Go-Live, Module by Module.
When a go-live fails, the dispute is who said it was ready. The benchmark to agree before work starts, three acceptance options and module-by-module checks.
• 12 min read
Read Article
Research notes
A Wrong Stock Figure Is Made Somewhere. Most Manufacturers Never Find Out Where.
A stock count corrects the record, not whatever made it wrong. What the public record shows on figures manufacturers cannot trust, four options, our benchmark.
• 12 min read
Read Article
Research notes
You Bought the Business, and Its Systems Came With It. Here Is What the Public Record Shows.
Systems that came with an acquisition stay unexplained while integration waits. What the public record shows, the options, and the benchmark we would set.
• 12 min read
Read Article
Research notes
You Cannot Hire for Your Old System. You Can Stop Needing To.
Retention pay, contractors, retraining or a packaged product: each answers a skills shortage for a while. The four options weighed, and the benchmark we set.
• 10 min read
Read Article
Research notes
Your Contract's End Date Means Little Until You Can Describe Your Own System. Four Ways Forward, Weighed.
Many public systems can be described only by their supplier. Four ways forward at a contract's end date, weighed, and what each one risks.
• 12 min read
Read Article
Research notes
Your Launch Has Been "Next Quarter" for Two Years. The Blocker Has Never Been Named.
A launch stuck at next quarter usually waits on an old system nobody has opened. What the public record shows, the options, and the benchmark we set.
• 10 min read
Read Article
Research notes
Your Oldest Server Stays Because One Application Cannot Leave It. Four Ways Out, Weighed.
An old server often stays for one application that runs nowhere else. Four ways out, what each risks, and what waits while the machine stays.
• 12 min read
Read Article
Research notes
Your Releases Happen at Midnight, by Hand. Four Ways Out, Weighed.
A release done by hand at midnight makes releases rarer and riskier. What that holds back, four ways out weighed, and the benchmark for a repeatable release.
• 10 min read
Read Article
Research notes
Your Replacement Is One Programme With One Go-Live, Years Away. Here Is the Benchmark We Would Set.
One programme, one go-live years away, and nothing in use until then. Four ways to run a campus system replacement, weighed, and the benchmark we would set.
• 12 min read
Read Article
Research notes
Your Replacement Was Scoped From the Systems Everyone Could Remember. Here Is What the Public Record Shows.
A replacement scope set from memory leaves out much of what an institution runs. What the public record shows, four options weighed, and our benchmark.
• 12 min read
Read Article
Research notes
Your Security Fixes Are Waiting in a Queue. Here Is the Benchmark We Would Set.
Security fixes wait on old systems because nobody can see what they break. The benchmark we would set so your own team applies them as they arrive.
• 10 min read
Read Article
Research notes
Your Staff Are the Connection Between Your Systems. Here Is the Benchmark for Ending It.
When lending systems cannot talk, staff re-key data by hand. The benchmark we would set to end it, and the path: rebuild the one module that has to connect.
• 10 min read
Read Article
Research notes
Your Supplier's Contract Has an End Date You Cannot Use. Here Is What the Public Record Shows.
Public systems often stay with the supplier that built them, because only it can describe them. What we found, four options and the benchmark we would set.
• 12 min read
Read Article
Research notes
Your System Applies Its Rules Every Day. Nobody Can Say What They Are.
Many lenders apply rules every day that nobody can state. What the public record shows, what unwritten rules hold back, the options, and our benchmark.
• 10 min read
Read Article
Research notes
Your System Is "Not AI Compatible". That Is Where the Decision Starts.
Most regulated firms want AI and few use it. What stands between an old system and AI, four ways forward weighed, and the readiness benchmark we would set.
• 10 min read
Read Article
Research notes
Your Systems Are Already Joined, by Files, Scripts and Spreadsheets. Here Is the Benchmark We Would Set.
Nightly files, scripts and spreadsheets already join most logistics systems. The benchmark we would set for them, what we would rebuild, what we will not claim.
• 12 min read
Read Article
Research notes
Your System's Manual Describes a System That No Longer Exists. Here Is What the Public Record Shows.
Many public systems run on documents from the year they went live. What the record shows, four ways to get a true description, the benchmark we would set.
• 13 min read
Read Article
Research notes
Your Team Spends Its Year Keeping the Old System Alive. Here Is the Benchmark We Would Set.
Invoices are only part of what an old system costs; the rest is staff time nobody counts. Four ways to lighten the year, and the benchmark we would agree.
• 12 min read
Read Article
Research notes
A Public Service Should Not Rest on a Retirement Date. Four Ways Forward, Weighed.
You cannot tender for a skill nobody has. Four ways forward weighed, from extensions of service to writing the system down while its experts are still in post.
• 12 min read
Read Article
Research notes
"Accepted Again" Is Not a Plan. A Shrinking Register Is.
Past end of support, a new flaw has no fix and is accepted again. The benchmark we would set to close those gaps, and the order the exposed parts move.
• 10 min read
Read Article
Research notes
Before Old Data Moves, Someone Should Write Down Where It Cannot Be Trusted.
A new system starts with whatever the old one held, and its faults surface after go-live. The benchmark we would set for retail data before it moves.
• 11 min read
Read Article
Research notes
Before You Ask What a Replacement Costs, Ask What It Is Worth.
Three quotes to replace an old lending system, far apart. Why they differ, what they leave out, the ways to buy, and the benchmark for the budget decision.
• 9 min read
Read Article
Research notes
Every Booking System Has a Ceiling. Most Firms Learn Theirs in the Busiest Week.
The public record on booking and operating systems meeting their limits: what we found, why the weak part stays hidden, the options, and our benchmark.
• 12 min read
Read Article
Research notes
Every Crossing Between Your Systems Should Have an Owner. Here Is the Benchmark We Would Set.
Timed files, scripts and people join a retailer's systems, and nobody has listed them. The benchmark we would set for those crossings, and the path forward.
• 11 min read
Read Article
Research notes
Every Outage Was Resolved. The Record Is What the Regulator Reads.
Each bank outage is fixed and closed; together they form the record regulators act on. What the public record shows, the options, and our benchmark.
• 9 min read
Read Article
Research notes
Every Question About Your Old System Waits for One Person. Here Is the Benchmark We Would Set.
In many public bodies every question about an old system goes to one person. Four ways to answer them, weighed, and the benchmark we would agree first.
• 12 min read
Read Article
Research notes
Finished Should Mean Matched. The Benchmark We Would Set for a Replacement.
A replacement reported as seventy per cent complete can still be years from right. Our benchmark for replacing an old booking, dispatch or billing application.
• 12 min read
Read Article
Research notes
Know Which Part Gives Way First, and Move It Before the Next Peak
After a peak-day outage the choice looks like more hardware or a full replacement. Our benchmark instead: find the part that gives way first, and move it first.
• 10 min read
Read Article
Research notes
Lenders Do Not Fear Their Old Systems. They Fear One Weekend.
We reviewed the public record of system replacements in financial services: what lenders fear, what waiting costs in growth, and the benchmark we would set.
• 10 min read
Read Article
Research notes
Manufacturers Keep Their Old Applications for One Reason. It Is the Go-Live Day.
We reviewed manufacturers whose sales fell after a new system went live: why old applications are kept another year, four ways forward, and our benchmark.
• 12 min read
Read Article
Research notes
A New System Can Pass Every Test and Still Miss the Old One's Rules.
A new order and dispatch system can pass every test and still drop rules the old one applied for years. Four ways to know a part is ready, and our benchmark.
• 11 min read
Read Article
Research notes
Nobody Can Say How Much of Your Department Runs on Unsupported Systems. Here Is What the Public Record Shows.
Two national governments have counted their unsupported systems; most public bodies cannot. What the public record shows, the options, and our benchmark.
• 12 min read
Read Article
Research notes
"Nothing Will Be Lost" Is a Promise. A Benchmark Is Something You Can Check.
No one can honestly promise a new system does all the old one did. Here is the benchmark we would set before go-live, checked function by function.
• 9 min read
Read Article
Research notes
Off the Clipboard Starts With Counting the Copies.
Plant records are careful, then copied by hand into every system that needs them. The benchmark we would agree first, three ways off the clipboard, the path.
• 12 min read
Read Article
Research notes
Operators Know Which Servers Are Old. What Nobody Has Written Down Is What Runs on Them.
Billing and customer applications on servers past their makers' support: what the public record shows, why they stay, four ways forward, and our benchmark.
• 13 min read
Read Article
Research notes
Most Operators Say They Depend on Their Legacy Vendors. What Few Hold Is Their Own Record of What They Run.
Most operators say they depend on legacy vendors; few hold their own record of what they run. What the public record shows, four ways forward, our benchmark.
• 13 min read
Read Article
Research notes
The Plant Says One Number and the ERP Says Another. The Public Record Says That Is Where AI Pilots Stop.
Manufacturers whose figures do not travel between systems: what the public record shows, where figures cross by hand, why AI pilots stop there, ways forward.
• 12 min read
Read Article
Research notes
Retail Figures Are Not Wrong by Accident. Each One Is Made Wrong Somewhere.
The public record on retail stock, product and customer figures that cannot be trusted: what we found, why the cause stays hidden, four ways to respond.
• 11 min read
Read Article
Research notes
Retail Systems Rarely Share What They Know. The Connection Is Usually a Person.
Tills, website, stock and accounts that do not share what they know: what the public record shows, what waits while people carry the data, four ways forward.
• 11 min read
Read Article
Research notes
Your Systems Are Already Joined, by Scripts, Files and Spreadsheets. Here Is the Benchmark We Would Set.
A nightly program stopped and two courses showed last term's lists. The benchmark we would set for the scripts, files and hand-offs joining a campus's systems.
• 13 min read
Read Article
Research notes
Sharing One Record Should Not Mean Replacing Every System. Here Is the Benchmark We Would Set.
Hospitals are told sharing records means replacing the old system. The benchmark we would set first, and the order the parts that must exchange are rebuilt.
• 10 min read
Read Article
Research notes
The Advert Has Been Open for Months. A Software Firm Can Stop Waiting for the Old Skill.
Firms whose product runs on an old technology hire from a list that keeps shrinking. What that holds back, four ways forward weighed, and the one we recommend.
• 12 min read
Read Article
Research notes
Software Firms Say They Cannot Hire for Their Old Technology. What Holds Them Back Is How Few People Can Read the Code.
Software firms say they cannot hire for their old technology. The record points to how few people can read the code. What we found, and four ways forward.
• 13 min read
Read Article
Research notes
Spares Buy Time, Not a Way Off. Four Ways to Deal With Servers Past Their Support, Weighed.
New servers arrive, most applications move, and one or two keep the old machines on. Why spares and extended support buy time, and four ways forward, weighed.
• 12 min read
Read Article
Research notes
Hospital Systems Rarely Pass Records to Each Other. The Connection Is Usually a Person.
We reviewed the public record on old hospital systems that cannot exchange records: what we found, what waits while staff carry records, and four ways forward.
• 11 min read
Read Article
Research notes
The Day the Plan Changes Is the Day That Counts. Here Is the Benchmark We Would Set.
Servers were doubled and the dispatch screen still froze when a road closed. The benchmark we would set for an old dispatch system before the next bad day.
• 12 min read
Read Article
Research notes
The Fees Office Says Paid and the Examination Section Says Due. Here Is What the Public Record Shows About Separate Systems.
Admissions, fees, examination and records systems that do not share: what the public record shows about colleges and universities, the options, our benchmark.
• 13 min read
Read Article
Research notes
The Fix for Your Old Systems Is Too Big to Fund as One Project. Here Is the Benchmark We Would Set.
Money comes at once for a failure, rarely for removing its cause. Four ways to fund the exit from old systems, weighed, and the benchmark we would agree first.
• 11 min read
Read Article
Research notes
The People Who Understand Your Oldest System Are Retiring. Here Is What the Public Record Shows.
The people who understand government's oldest systems are retiring, and what they know is written nowhere. What the public record shows, options, our benchmark.
• 12 min read
Read Article
Research notes
The Weeks That Earn the Year. More Servers Are One Answer of Four.
An application sized for an ordinary week meets the season with the same capacity. Four answers weighed: more servers, a hosting move, a product, or a rebuild.
• 12 min read
Read Article
Research notes
Tied a Little Tighter Every Year. Where Your Dependence on a Vendor Is Now, and Where It Should Be.
Every portal, plan and report reaches the vendor's billing product its own way, and nobody counts the ties. Our benchmark, so the dependence stops growing.
• 13 min read
Read Article
Research notes
Unsupported Software Is Now a Board Matter. Most Firms Cannot Say Where It Is.
Regulators now treat software past its end of support as a board matter, yet most lenders cannot say where it runs. What we found, the options, our benchmark.
• 10 min read
Read Article
Research notes
You Were Told a Web Version Means Rebuilding the Whole Product First. It Can Reach the Web One Module at a Time.
A web version of a desktop product is usually planned as one big rebuild and launch. What that costs a software firm while it waits, four ways forward weighed.
• 13 min read
Read Article
Research notes
The Old System Still Works. That Is Why the Replacement Never Starts.
The public record on why firms keep old systems and how long replacing operations software takes: what we found, four ways forward weighed, our benchmark.
• 12 min read
Read Article
Research notes
Your Busiest Days Are Your Growth Days. Old Systems Fail on Them.
Payday, month end and festival season are when a lender grows, and when old systems fail. What that costs, four ways to prepare, and our benchmark.
• 10 min read
Read Article
Research notes
Your Software's Maker Has Set the Date. The Plan Can Still Be Yours.
Extended support buys time and nothing else. What staying on software past its maker's date costs a lender, four ways to answer the letter, and our benchmark.
• 9 min read
Read Article
Case Study
The Pre-Acquisition Code Audit Most Buyers Skip
Buyers scrutinise financials and legal, then inherit the software blind. Here's the pre-acquisition code audit that reveals what the spreadsheet can't.
• 6 min read
Read Article
AI/ML
What an AI-Augmented Engineering Team Actually Looks Like
AI-augmented engineering isn't a chatbot bolted onto a dev team. Here's what it actually looks like in day-to-day practice—and what it deliberately isn't.
• 6 min read
Read Article
DevOps
Designing an IoT-to-Cloud Data Pipeline That Survives Scale
IoT pipelines that work with ten devices collapse at ten thousand. Here's how to design a device-to-cloud data pipeline that actually survives real scale.
• 6 min read
Read Article
AWS & Cloud
A Cloud Cost Audit Playbook That Finds Real Savings
Most cloud cost advice is generic and useless. Here's a concrete, step-by-step cloud cost audit playbook that finds the real money hiding in your AWS bill.
• 6 min read
Read Article
AI/ML
RAG in Production: Where It Actually Breaks
Retrieval-augmented generation demos beautifully and fails quietly in production. Here are the real failure modes—and how to build RAG that holds up.
• 5 min read
Read Article
Full-Stack
The Gap Between a Working MVP and a Production System
A demo that works is not a system you can run. Here's the real distance between an MVP and production—and why teams underestimate it every single time.
• 5 min read
Read Article
Full-Stack
Inheriting a Messy Codebase: A 90-Day Plan
You've inherited a codebase nobody documented and the last engineer left. Here's a disciplined 90-day plan to go from fear to control without a rewrite.
• 5 min read
Read Article
AI/ML
Five Signs Your AI-Generated Codebase Needs a Rescue
AI-built codebases fail in predictable ways. Here are five early warning signs that a vibe-coded app is heading for trouble—and what to do before it stalls.
• 6 min read
Read Article
DevOps
The Handoff That Never Happens: Why Contractor Transitions Fail
The project is 'done.' The contractor disappears. Your team inherits a mystery. Here's why contractor handoffs fail—and the one thing that fixes it.
• 18 min read
Read Article
DevOps
Infrastructure as Code: Beyond the Buzzword
'We use Terraform' isn't the same as practicing Infrastructure as Code. Here's the maturity model that separates IaC theater from operational excellence.
• 16 min read
Read Article
DevOps
Scaling Without Breaking: The Checklist CTOs Need Before 10x Growth
Your system works at current load. Will it work at 10x? Here's the checklist of assumptions that break at scale—and how to find them before your customers do.
• 16 min read
Read Article
DevOps
Why We Open-Sourced Our Delivery Checklist (And Why Others Won't)
Most service companies guard their processes like trade secrets. We published ours on GitHub. Here's the counterintuitive reason why openness is competitive advantage.
• 14 min read
Read Article
DevOps
Why Your Engineers Hate Your Deployment Process
When engineers avoid deploying, your process is the problem. Here's what makes deployment processes hated—and how to build ones people actually use.
• 12 min read
Read Article
DevOps
Incident Postmortems That Actually Prevent Recurrence
Most postmortems fail to prevent recurrence. They focus on blame or bureaucracy instead of systemic improvement. Here's how to run postmortems that work.
• 15 min read
Read Article
Full-Stack
What Series B CTOs Wish They Knew at Series A
What Series B+ CTOs most often wish they had done at Series A. The patterns are consistent, and most are preventable. Here's the list.
• 14 min read
Read Article
DevOps
Why Your Staging Environment Lies to You
Works in staging, breaks in production. Here's why your staging environment lies—and how to make it tell the truth.
• 15 min read
Read Article
DevOps
Why DevOps Isn't a Role: The Organizational Pattern That Defeats Itself
Hiring a 'DevOps team' often creates the silos DevOps was meant to eliminate. Here's what DevOps actually means—and how to build the capability without the dysfunction.
• 16 min read
Read Article
AWS & Cloud
Why Your Startup's First AWS Architecture Decision Is the Most Expensive One
Early architecture choices compound for years. Here's how to avoid the five most common AWS mistakes that cost startups $100K+ in rework - and what to do instead.
• 22 min read
Read Article
Full-Stack
The Knowledge Transfer Nobody Does (And Why Projects Fail 6 Months Later)
Your contractor delivered the code. Six months later, nobody knows how it works. Here's why knowledge transfer is the most skipped step in software delivery - and what a real handoff looks like.
• 25 min read
Read Article
Security
HIPAA in the Cloud Isn't a Checkbox: What HealthTech CTOs Actually Need
Using AWS doesn't make you HIPAA compliant. Here's what HealthTech CTOs actually need to know about cloud compliance - from BAAs to audit trails to the gaps most teams miss.
• 31 min read
Read Article
AWS & Cloud
The Vendor Lock-In Myth: Why Multi-Cloud Often Costs More Than It Saves
The fear of AWS lock-in drives companies to multi-cloud strategies that cost more and deliver less. Here's when lock-in is real—and when it's an excuse.
• 9 min read
Read Article
AI/ML
When AI Gets It Wrong (And Why That's Expected)
AI makes mistakes. Regularly. Here's what kinds of mistakes to expect, why they happen, and why the answer isn't less AI—it's better human review.
• 8 min read
Read Article
Security
The SOC2 Shortcut That Isn't: Why Compliance Requires Systematic Process
Every startup wants the SOC2 shortcut. Here's the uncomfortable truth: shortcuts create compliance debt that costs 3x more to fix than doing it right.
• 9 min read
Read Article
DevOps
Why Your Monitoring Dashboard Is Lying to You
Your dashboards are green. Everything looks fine. Then production breaks and you have no idea why. Here's what your monitoring isn't telling you.
• 11 min read
Read Article
Full-Stack
The Senior Tax You Should Be Happy to Pay
Senior engineers cost 2-3x more than juniors. Here's why that 'tax' is the best investment you'll make—and what happens when you try to avoid it.
• 10 min read
Read Article
DevOps
Technical Debt Isn't What You Think It Is
Everyone focuses on code quality when discussing technical debt. But the debt that kills startups isn't in the code—it's in everything around it.
• 10 min read
Read Article
Security
Security Theater vs. Security Reality
Passing an audit isn't the same as being secure. Here's how to tell if you have real security or just impressive-looking checkbox compliance.
• 16 min read
Read Article
DevOps
Why Your CI/CD Pipeline Is Slower Than It Should Be
Slow pipelines aren't inevitable. Most slowness comes from fixable patterns that accumulate over time. Here's what's slowing you down and how to fix it.
• 17 min read
Read Article
AI/ML
The 45-Minute Review That Pays for Itself
A worked example: AI writes a data pipeline in ten minutes, and a 45-minute senior review catches a query pattern that would cost far more at scale. How the numbers add up, and what to check.
• 18 min read
Read Article
AWS & Cloud
What Your AWS Bill Is Actually Telling You
Your AWS bill isn't just a cost report. It's a diagnostic tool revealing architecture decisions, team behaviors, and hidden waste. Here's how to read it.
• 15 min read
Read Article
DevOps
The 2AM Test: Is Your Infrastructure Production-Ready?
The real test of infrastructure isn't performance benchmarks. It's what happens when something breaks at 2AM. Here's the checklist that separates ready from risky.
• 24 min read
Read Article
AI/ML
AI Drafts, Seniors Decide: Human Accountability in AI-Augmented Development
The AI wrote the code in 10 minutes. The review took 45. Here's why that ratio is exactly right - and why 'AI does everything' is the wrong message.
• 36 min read
Read Article
DevOps
What 'Done' Actually Means: The Complete Delivery Checklist
Most contractors hand you a repo link and call it done. Here's what a production-ready delivery actually includes - and why code alone is technical debt.
• 36 min read
Read Article
Explore by Topic
Dive into specific areas of expertise
☁️
AWS & Cloud
🤖
AI/ML
⚙️
DevOps
💻
Full-Stack
🔒
Security
📊
Case Study
🔎
Research notes
Newsletter
What We Advised Against
The AI and legacy-system changes we recommended not making, why, and what we suggested instead. A short read every other Monday.
Subscribe on LinkedInReady to Build Something Great?
Our team brings the same systematic approach from these articles to every client project.