How Project Work Is Structured
Project engagements are scoped around a specific objective: audit your AWS costs, review your architecture for security and scalability, or migrate a workload to a modern stack. Each project has a defined scope, timeline, deliverables, and price agreed upon before work begins.
This model is a good fit when you have a clear problem to solve or a specific initiative to execute, and you want an experienced architect to lead or support that effort from start to finish.
Common Project Types
AWS Cost Audit
A focused review of your AWS bill and architecture to identify savings opportunities. Most clients find $5K–$50K/year in quick wins.
Typically 1–2 weeks · Starting at $2,500
Architecture Review
Security, scalability, and cost analysis of your AWS setup. You receive a detailed findings report and a prioritized improvement roadmap.
Typically 2–3 weeks · Starting at $5,000
Migration & Modernization
Move .NET or Node.js applications to serverless or containers on AWS. Includes assessment, planning, implementation, and knowledge transfer.
Timeline varies · Custom quote
These are the most common starting points, but project scope is always tailored to your situation. If your need doesn't fit neatly into one of these categories, let's talk about it.
How Scoping Works
Every project starts with a conversation. Before any commitment, we'll discuss your goals, constraints, and timeline to determine whether a project engagement is the right approach and what the scope should look like.
Discovery Call
A free 25-minute conversation to understand your situation, goals, and constraints. No obligation.
Written Proposal
A clear document outlining scope, deliverables, timeline, pricing, and payment schedule. You know exactly what you're getting.
Execution & Delivery
Work begins after agreement and initial payment. Regular check-ins keep you informed throughout.
Pricing Approach
The pricing model depends on how well-defined the scope is. I use whichever approach best protects both sides from surprises.
Fixed Price
Used for well-defined engagements where the scope, deliverables, and timeline are clear upfront. Cost audits and architecture reviews typically fall here.
You know the total cost before work begins.
Time & Materials
Used for work where the scope may evolve as we learn more: migrations, modernization efforts, or complex infrastructure changes. Billed at an agreed hourly rate.
Flexibility to adapt as the project unfolds.
Hybrid Approach for Larger Projects
For larger or more complex initiatives, I often recommend a hybrid: a fixed-price discovery or assessment phase to define the full scope, followed by time & materials for implementation. This gives you a clear picture of the work before committing to the larger investment, and gives me enough understanding to provide accurate estimates.
Payment Structure
Payment is structured to keep risk manageable for both sides. I don't ask for full payment upfront, and I don't work for weeks without compensation. The specifics depend on the project size and pricing model.
Fixed-Price Projects
| Small projects | Under $5,000: Payment in full before work begins. |
| Mid-size projects | $5,000–$15,000: 40% deposit to begin, 40% at a defined midpoint milestone, 20% upon delivery. |
| Larger projects | Over $15,000: Milestone-based payments structured so that no more than two weeks of work is unbilled at any point. |
Time & Materials Projects
Invoiced biweekly or monthly, depending on the engagement. Payment is due within 15 days of invoice. A deposit equivalent to the first two weeks of estimated work is required before the engagement begins.
Final Deliverables
Final deliverables (reports, documentation, architecture diagrams, code repositories) are provided upon receipt of final payment. Work product created during the engagement is shared incrementally as milestones are completed.
Payment Methods
- Credit card
- Debit card
- ACH bank transfer
- Wire transfer (details provided upon request)
What You Walk Away With
Every project includes tangible deliverables. The specifics depend on the engagement type, but you should always expect to receive documentation and knowledge transfer, not just a verbal recommendation.
Audits & Reviews
- • Written findings report
- • Prioritized recommendations with estimated impact
- • Architecture diagrams (current state and proposed)
- • Walkthrough session with your team
Migrations & Implementation
- • Working infrastructure and application code
- • CI/CD pipeline configuration
- • Runbooks and operational documentation
- • Knowledge transfer sessions with your team
Scope Changes
Requirements evolve. If the scope needs to change during a project, here's how it's handled:
| Minor adjustments | Small shifts in priority or approach within the existing scope are normal and expected. These don't require a formal change. |
| Material changes | If the scope expands significantly (new systems, additional environments, different requirements), I'll provide a written change order with revised pricing and timeline before proceeding. |
| No surprises | I will never bill for work outside the agreed scope without discussing it first. If I see scope creep developing, I'll flag it early. |
Common Questions
How long does a typical project take?
Cost audits typically take 1–2 weeks. Architecture reviews run 2–3 weeks. Migrations and modernization projects vary widely, from a few weeks to several months depending on complexity. The proposal will include a realistic timeline.
Can a project turn into a fractional engagement?
Absolutely. Many clients start with a cost audit or architecture review and then move to a fractional retainer for ongoing support. The project gives both sides a chance to evaluate the working relationship.
What if the project uncovers more work than expected?
This is common, especially with architecture reviews. The initial engagement will surface findings and recommendations. If you want to act on those recommendations, we can scope follow-on work as a separate project or fold it into a fractional engagement.
Do you require an NDA?
I'm happy to sign a mutual NDA before any engagement. If your organization has a standard NDA, send it over and I'll review it. Confidentiality is a baseline expectation regardless of whether a formal NDA is in place.