Selected engagements.
Anonymized case studies. Client names withheld; outcomes are real.
Federal evaluators can request fuller references via contracts@hyamsdigitalsolutions.com.
Regional contractor, ~$30M revenue, ops team of 30+.
Problem
Sales pipeline and project operations data lived in disconnected systems. No closed loop between Sales-stage activity and on-the-ground project metrics.
What we built
- Dynamics 365 Sales rebuild aligned to the actual sales process
- Power BI semantic model and dashboards across Sales + Operations
- Foundation ETL pipeline integrating CRM, project mgmt, and accounting
Outcome
Closed sales/ops data loop. 30+ daily Power BI users. Ops leadership now sees pipeline-to-project-margin in one view.
Regional firm, 40+ attorneys, partner-led.
Problem
Case-relevant correspondence buried in 17,000+ emails across attorneys. Finding the right thread when needed took hours.
What we built
- Secure M365 email pipeline with controlled retention
- RAG search layer over the email corpus with citations back to source threads
- Audit-ready access logging
Outcome
Minutes-to-answer for case-relevant correspondence. Search results return with thread citations attorneys can verify.
Startup serving regulated industries, US-based.
Problem
FinCEN BOI / RER filing required a defensible end-to-end workflow per tenant, with full audit trail and submission status tracking.
What we built
- Multi-tenant filing platform with role-based access
- Submission engine integrating with FinCEN endpoints
- Full audit trail per filing event
Outcome
End-to-end submission workflow live. Tenants file and track without leaving the platform. Audit trail satisfies regulator-readiness.
Producer-led brokerage, 20+ agents, multi-market.
Problem
Deal tracking lived in spreadsheets per producer. No firm-wide pipeline visibility. Replacement tools were either too heavy (enterprise CRE) or too generic (Salesforce).
What we built
- Deal tracking platform tuned to CRE-specific stages
- Producer-level + firm-level pipeline views
- Lightweight document hub per deal
Outcome
Firm-wide pipeline visibility. Producers keep their workflow; leadership gets the rollup.
Owner-operated, four locations, multi-year tenant base.
Problem
Rent, tenants, and late fees were tracked in a spreadsheet with twelve monthly tabs per year. Reconciling a single tenant history meant opening a dozen tabs, and nothing enforced the late-fee rules consistently.
What we built
- Tenant, unit, and payment model covering all four locations
- Rent roll and late-fee handling applied by rule instead of by hand
- Multi-year ledger with per-tenant payment history
Outcome
The spreadsheet is retired. Rent status across every location resolves in one view, and late fees apply consistently without the owner recalculating them.
Owner-operated clinical practice, two service lines.
Problem
Web presence, local search, and reviews were handled ad hoc across two service lines. No single place showed whether any of it produced patients, so marketing spend was defended by anecdote.
What we built
- Custom sites per service line with structured data and local search groundwork
- Review and reputation workflow tied to the practice profile
- Command center reporting rankings, reviews, traffic, and inbound leads together
Outcome
Presence and performance sit in one dashboard. The practice can see which service line is producing inbound interest instead of inferring it.
Operations teams dependent on vendor platforms with difficult APIs.
Problem
Core business data was locked behind billing, telecom, and PSA platforms whose APIs paginate inconsistently, encode fields as opaque integer picklists, and return success codes on authentication failures.
What we built
- Typed async clients handling pagination, rate limits, and picklist resolution
- Model Context Protocol servers exposing those systems to AI tooling directly
- Middleware layer normalizing vendor payloads into a stable internal shape
Outcome
Operations data is queryable in one interface instead of three portals, and the same clients back both automation and assistant workflows.
The infrastructure behind the delivery.
Built and run by HDS for HDS. Listed here because it is what makes the engagement velocity above possible, not as past performance.
What we built
- Multi-agent orchestration platform with persistent memory
- Code review + verification gates as first-class agents
- Audit-grade logging of every agent action
HDS ships engagements at multi-engineer velocity with one principal. The agents that built this site are the same ones used in client work.