Value-Based Engagement
I price outcomes, not inputs. Whether through ongoing partnerships or fixed-price projects, you know what you're investing and what you're getting.
The Problem with Hourly Billing
For years, I billed by the hour like most consultants. But I found this model increasingly misaligned with how value is actually created.
The hourly model penalizes efficiency. If I solve your problem elegantly in 6 hours instead of 20, you shouldn't get less value - you should get more. Yet hourly billing makes it seem like you're getting less.
The hourly model obscures value. Architecture and strategic thinking are incredibly valuable, but when buried in hourly billing, their impact gets averaged out across mundane execution work.
The hourly model creates wrong incentives. You want me to solve problems efficiently. Hourly billing incentivizes the opposite.
So I changed how I work.
Two Ways to Work Together
Option 1: Systems Partnership (Retainer)
Best for: Ongoing technical needs and mission-critical systems
A Systems Partnership isn't about buying hours - it's about having a trusted technical partner who knows your business and systems intimately.
What You Get
System Stewardship
- Proactive monitoring and maintenance
- Security updates and performance optimization
- Regular health checks and improvements
- Database optimization and technical debt reduction
Strategic Guidance
- Architecture and design consultation
- Technology selection and planning
- Monthly strategy sessions
- Long-term technical roadmap development
Priority Access
- Rapid response for critical issues
- Direct communication channel
- Predictable availability when you need it
Continuous Improvement
- Regular feature enhancements
- Process optimization
- Emerging opportunity identification
- System evolution aligned with business growth
How It Works
- Initial Consultation - We discuss your systems, needs, and goals
- Partnership Design - I propose a retainer structure tailored to your situation
- Ongoing Engagement - Monthly partnership with regular delivery and communication
- Monthly Reporting - Clear reporting on deliverables and outcomes (not hours)
Investment: $3,000-$8,000/month depending on scope and complexity
This Isn't Measured in Hours
You're not buying time blocks. You're getting comprehensive technical partnership with predictable monthly investment. Some months I might spend more time, some less - but the value you receive remains consistent and high.
Option 2: Fixed-Price Projects
Best for: Specific initiatives with defined scope
From modernizing legacy systems to building new APIs, I deliver project outcomes at fixed prices based on complexity, not estimated hours.
The Process
1. Discovery Phase (Optional but Recommended)
For non-trivial projects, I recommend starting with a dedicated discovery engagement:
- Domain analysis and requirements gathering
- Technical specification and architecture design
- Risk assessment and mitigation planning
- Detailed implementation roadmap
Investment: $10,000-$15,000
Deliverable: Comprehensive technical specification and fixed-price implementation proposal
Why start here? This ensures we're solving the right problem in the right way, and gives both of us confidence in the implementation pricing.
2. Implementation Phase
Based on the discovery work (or for straightforward projects, initial consultation), you receive a fixed-price proposal broken into:
- Clear deliverables and success criteria
- Timeline and milestones
- Total investment
- Payment structure
Complexity-Based Pricing
Tier 1: Straightforward - $2,500-$5,000
Well-defined features using established patterns. Clear scope with minimal unknowns.
Examples: New reports, simple CRUD endpoints, minor enhancements
Tier 2: Moderate - $5,000-$12,000
Requires design thinking and integration work. Some stakeholder coordination needed.
Examples: New workflows with business rules, third-party integrations, data migrations
Tier 3: Significant - $15,000-$30,000
Architectural implications and domain modeling required. High coordination needs or complex business logic.
Examples: New subsystems, complex domain features, major refactoring
Tier 4: Strategic - Custom Engagement
Requires dedicated discovery to scope properly.
Examples: Complete system modernization, multi-phase consolidation programs, platform migrations
3. Delivery & Knowledge Transfer
- Working software that meets specifications
- Comprehensive documentation
- Code walkthroughs and knowledge transfer
- Post-delivery support period
What You Can Expect
Transparent Communication
Regular updates on progress, challenges, and decisions. You're never left wondering what's happening.
Quality Delivery
Clean, maintainable code following modern .NET best practices. Systems built to last and evolve.
Strategic Thinking
Not just executing tasks, but thinking critically about the problem and finding the best solution.
Honest Counsel
If I think you're approaching something wrong, I'll tell you. If there's a simpler solution, I'll recommend it even if it means less revenue for me.
Predictable Investment
Whether retainer or fixed-price, you know what you're investing upfront. No surprise invoices.
Frequently Asked Questions
What if a retainer month is quiet and you don't use much of your allocated time?
That's fine - you're paying for availability and peace of mind as much as active work. Some months are quieter, some are busier. It averages out, and you always have priority access when needed.
What if a project takes longer than expected?
For fixed-price projects, I absorb that risk. That's why discovery phases are valuable - they reduce uncertainty. But if scope changes or expands, we discuss that explicitly.
Can I start with a project and move to a retainer later?
Absolutely. Many of my long-term partnerships started with a single project. It's a great way to build trust and see if we work well together.
Do you work on-site or remotely?
[YOUR PREFERENCE - remote, hybrid, on-site options]
What size projects do you take on?
I work best with projects starting around $5,000 and up. For smaller needs, I can sometimes accommodate within an existing retainer relationship.
What if we need to pause or end the partnership?
Retainers are typically [NOTICE PERIOD - e.g., 30-day notice]. Professional relationships should be mutually beneficial - if it's not working, we should part ways respectfully.
How do you handle urgent issues?
Retainer clients get priority response - typically within [TIMEFRAME - e.g., 4 hours for critical issues]. For project clients, we can discuss SLA requirements.
"I'm incentivized to solve your problems elegantly and efficiently - which is exactly what you want."
— On value-based engagement
Ready to Discuss Your Needs?
Let's talk about how I can help