<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Case studies on BDS — Mid-Market IT Consulting</title><link>https://bds-staging-9um.pages.dev/case-studies/</link><description>Recent content in Case studies on BDS — Mid-Market IT Consulting</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bds-staging-9um.pages.dev/case-studies/feed.xml" rel="self" type="application/rss+xml"/><item><title>SaaS Platform Migration from Colocation to AWS — Engagement Archetype</title><link>https://bds-staging-9um.pages.dev/case-studies/saas-colo-to-aws-migration/</link><pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate><guid>https://bds-staging-9um.pages.dev/case-studies/saas-colo-to-aws-migration/</guid><description>&lt;p&gt;&lt;em&gt;This is a representative engagement archetype — not a disclosure of a specific client or past project. It describes the kind of work this practice is built to execute, the shape of a typical engagement in this category, and the outcomes such an engagement is scoped to deliver.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-situation-this-archetype-addresses"&gt;The situation this archetype addresses&lt;/h2&gt;
&lt;p&gt;A growth-stage SaaS company (roughly 100-250 employees, $15-35M ARR range) running on colocation infrastructure enters late-stage acquisition discussions. The buyer&amp;rsquo;s technical diligence flags the colocation hosting as a risk — absence of cloud-native operational maturity, concentration in physical facilities, dependencies on aging hardware approaching end-of-life.&lt;/p&gt;</description></item><item><title>HIPAA Audit Readiness in 90 Days — Engagement Archetype</title><link>https://bds-staging-9um.pages.dev/case-studies/healthcare-hipaa-readiness/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://bds-staging-9um.pages.dev/case-studies/healthcare-hipaa-readiness/</guid><description>&lt;p&gt;&lt;em&gt;This is a representative engagement archetype — not a disclosure of a specific client or past project. It describes the kind of work this practice is built to execute, the shape of a typical engagement in this category, and the outcomes such an engagement is scoped to deliver.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-situation-this-archetype-addresses"&gt;The situation this archetype addresses&lt;/h2&gt;
&lt;p&gt;A healthcare technology company (roughly 150-300 employees, providing a clinical workflow or patient-data platform used by hospital systems or health plans) has scheduled a HIPAA Security Rule audit as a customer-driven requirement. An enterprise customer has conditioned contract renewal on a clean HIPAA audit within ninety days.&lt;/p&gt;</description></item><item><title>NetSuite Implementation for Mid-Market Manufacturing</title><link>https://bds-staging-9um.pages.dev/case-studies/manufacturer-netsuite-erp/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://bds-staging-9um.pages.dev/case-studies/manufacturer-netsuite-erp/</guid><description>&lt;p&gt;&lt;em&gt;This is a representative engagement archetype — not a disclosure of a specific client or past project. It describes the kind of work this practice is built to execute, the shape of a typical engagement in this category, and the outcomes such an engagement is scoped to deliver.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="why-this-is-an-archetype-and-not-a-named-case-study"&gt;Why This Is an Archetype and Not a Named Case Study&lt;/h2&gt;
&lt;p&gt;Searches for a NetSuite manufacturing case study usually want one of two things: proof that a firm
has done this before, or a realistic picture of how the project actually runs. This page answers the
second and deliberately does not attempt the first.&lt;/p&gt;</description></item></channel></rss>