Independent cloud engineering consultancy

Senior cloud engineering without the traditional MSP overhead.

I help organizations operate, clean up, modernize, and automate their cloud environments through direct access to experienced, hands-on engineering.

Standard rate
$150 / engineering hour
Service hours
Mon–Fri · 8am–5pm CT
Josh Sanches, Cloud Architect
Josh SanchesCloud Architect · Direct from assessment through implementation
Project-based and ongoing support engagements

A more direct model

The cloud architect in the room stays with the work.

There is no handoff from sales to an unfamiliar delivery team. I work directly with your stakeholders to understand the environment, surface the right priorities, and carry the engineering through.

Engagements are intentionally flexible: begin with a cloud-environment review, solve a defined problem, or establish an ongoing base of senior engineering capacity.

Service catalog

Support for the cloud you have—and the environment you want next.

Choose ongoing support, a focused assessment, or a defined block of engineering capacity. Each engagement can stand alone or become part of a longer roadmap.

02

Customer Onboarding

$4,000 one time

A structured start for Base customers: access, cloud context, account and identity review, immediate risk identification, environment inventory, and a prioritized work backlog.

Required for new Support Base customers; complex environments may need revised scope.

03

Cloud Environment Review & Cleanup Plan

Approx. $8,000

A 2–4 week assessment of spend, waste, security, resilience, technical debt, and operational practices—with prioritized findings and a practical remediation roadmap.

Final scope and price are confirmed before work begins.

04

AI Workflows & Cloud Modernization

$8,000 / 40 hours

Focused discovery and engineering for a practical AI workflow, automation, integration, prototype, limited production implementation, or modernization roadmap.

Usage, licensing, and third-party costs are separate; additional work requires approval.

05

Disaster Recovery Design

Scoped to your environment

Recovery architecture, system priorities, runbooks, and an implementation roadmap built around critical dependencies, recovery objectives, backup, and restoration needs.

Design, implementation, documentation, and exercises can be scoped separately.

06

Infrastructure as Code Transformation

$8,000 / 40 hours

A phased conversion of manually managed infrastructure into repeatable, version-controlled code, starting with the highest-value systems and workflows.

Additional phases are estimated separately; approved additional time is $150/hour.

07

Quarterly FinOps & Cloud Health Review

$2,000 / review

A recurring view of spend, anomalies, idle resources, savings opportunities, access, exposure, backup, monitoring, and newly accumulated technical debt.

Includes up to 15 engineering hours and is available as a Base add-on.

Transparent engineering rate

Project and retainer overages require customer approval and are billed at $150/hour in 30-minute increments.

Discuss scope

AWS AI & Automation

Practical AI workflows, built into your AWS environment.

Start with a defined use case and a small proof of concept when it makes sense. When it proves valuable, the work can grow into a secure, monitored workflow your team can support.

Bedrock applications

Focused internal chat, question-answering, drafting, structured extraction, and AI features connected to the systems your team already uses.

Private knowledge assistants

Useful answers from approved company documents, technical references, support material, and runbooks—with references back to the source material.

Intelligent document processing

Turn PDFs, forms, invoices, receipts, reports, and scanned documents into structured workflows with validation and human review where it matters.

Content & media intelligence

Transcribe and summarize recorded audio, extract decisions and action items, classify text, or route image content based on what the workflow finds.

AI-assisted cloud operations

Make alarms, logs, incident timelines, cost changes, security findings, and runbooks easier for operators to understand and act on—with human review in the loop.

Secure AI deployment

Move an approved workflow into a supportable AWS environment with least-privilege access, guardrails, monitoring, cost controls, infrastructure as code, and handoff documentation.

How it works

Clear movement from question to working outcome.

Every engagement is shaped around the environment, the work that matters now, and what should happen next.

  1. 01

    Assess

    Understand the environment, operating context, constraints, and the business impact behind the work.

  2. 02

    Prioritize

    Turn findings into a visible, practical sequence based on risk, value, effort, and dependencies.

  3. 03

    Implement

    Complete focused engineering work with clear scope, documentation, validation, and customer approval.

  4. 04

    Support

    Continue through a defined project, monthly engineering capacity, or a recurring cloud health review.

Why direct

Senior expertise, without layers between the problem and the person solving it.

Traditional MSPs can be the right fit for broad coverage and large support operations. This model is for organizations that value focused senior engineering, direct accountability, and the freedom to engage only the capacity they need.

See if the model fits

Direct engineering access

You work with the person assessing the environment, making the changes, and explaining the tradeoffs.

Right-sized engagements

Start with a focused review, a defined block of engineering capacity, or an ongoing monthly base.

Visible priorities

Recommendations are organized around real risk and value—not bundled into an opaque service package.

Transparent commercial model

Starting prices, included hours, scope boundaries, and approval requirements are clear before work proceeds.

Start with a conversation

Bring the environment, the problem, or the idea.

We can start by talking through your cloud environment, reviewing what needs attention, and deciding whether a focused assessment or engineering engagement makes sense.