You’re the CTO of a company built on .NET, neck deep in technical debt, and you’re worried your inherited .NET Monolith can’t scale with the business’s needs.
You’re feeling pressure to meet business deadlines, and your inherited .NET monolith can’t keep up.
Outages at critical times, hard to diagnose bugs, and a months’ long backlog of technical debt creates pressure for you with the business, especially sales.
Your team wants to pursue a costly big-bang rewrite, believing the new system will not have these problems.
Imagine having scalable software without a costly big-bang rewrite
Imagine being able to respond effortlessly when your sales team asks you for new features.
Imagine feeling confident that your system can scale to handle your business’s needs.
Imagine knowing you can add new features without adding to the backlog of technical debt.
Imagine keeping the monolith in place, and build your new system around it.
Keep what’s making you money and discard what costs hundreds of people-hours to maintain, without a big bang rewrite.
Get a personalized scaling roadmap for your system from a veteran .NET Solutions Architect
Get a plan to scale your .NET Monolith. You have the people, you have the pieces, but you don’t quite know the most effective and efficient way to fix what seem to be intractable problems with your .NET Monolith. Book a free 15 minute call with me to see if I can help you. Why?
- I’ve saved .NET teams millions of dollars by providing novel architectural solutions to often seemingly intractable problems
- I’ve worked with large .NET systems for over 16 years
- I’ve singularly positioned myself and my business to be aligned with your success. If you don’t get a win, neither do I.
Ok, so how does this work, anyway?
Our roadmapping sessions will take place over Zoom. There are three ninety minute calls that take place at kickoff, after interviews are complete; and at delivery. In between we’ll schedule one-on-one calls with the right people in your company as needed. You’re welcome to record any and all of these sessions, and I record and transcribe these sessions to ensure I can listen actively during the interviews and to help improve how I help you.
On our kickoff call, we’ll first define the current state of your business; what business pains you’re experiencing with the state of your .NET Monolith, and what technical, organizational and operational pains you’re feeling because of your monolith. We’ll identify constraints and road-blocks that have kept you from reaching your goals, and we’ll use those as a framework to go in-depth on your pains in individual interviews with business and technical stakeholders. Most importantly, we’ll agree on your business goals for your technical organization and systems.
In the individual interviews, we’ll dive into the specific manifestations of the pains, and accomplish two goals: 1) determine what paths can help your team resolve these pains; 2) ensure the roadmap captures the constraints and approaches that will work and more importantly — won’t work in your company.
Within a week of the last 1-1 interview, I will deliver a personalized, specific, roadmap for reaching your goals.
Sample Roadmap Outline
Would you like to see a sample? Each roadmap is confidential, but I’ve put together a sample outline using Brookfield Industries, a competitor to Contoso, Microsoft’s fictional example company:
Ready to Get Started?
Are you ready to scale your .NET Monolith? To be free of the pain that’s holding you back from helping your business achieve its potential? Great! The first step is to schedule a free 15 minute call where we make sure we’re a good fit to work together. The price for the roadmap is $9,995, which distinguishes teams from this-is-a-problem-but-we’re-going-to-keep-limping-along from teams that are frustrated and willing to make an investment to fix the underlying problems with their .NET Monolith that keep their teams from reaching their full potential.
In the 15 minute free no-sales call, we’ll talk about where your business and .NET Monolith is now, what pains you’re experiencing, and we’ll determine — together — whether or not I can help free you from the pain you’re feeling — that pit-in-your-stomach-feeling of not knowing when the next crisis with your .NET Monolith will come along, but knowing it will.
100% Money-Back Guarantee!
I’m so sure I can provide at least one high-value approach to solving your .NET monolith woes that I offer a 100% money-back guarantee. If at the end of our roadmapping engagement, you feel like I haven’t delivered on this promise, just let me know and I’ll refund your payment in full.
Still Have Questions?
What happens after the free fifteen minute call?
By the end of the call we’ll know if we’re a good fit. Within one business day, I’ll email you with payment instructions.
What happens after I pay?
Once you submit payment, you’ll receive a link to schedule an appointment on my calendar. The initial kickoff call typically will be about 90 minutes, but we’ll schedule 2 hours just in case. We’ll schedule 1-1 interviews with all the people who crucial to fixing these issues: CEO, CTO, Architect, Sales — whoever we need to talk to to be sure we solve the problems at hand.
How do I know if this will work?
You’re here because what you’ve tried in the past hasn’t worked. I’m here to help guide you to a way that will work given your context. There are no guarantees (except for the money back guarantee, of course) and nothing is written in stone, but if doing nothing was a valuable strategy you wouldn’t be reading these words right now.
I’m nervous about reviewing our architecture, codebase, and business with a consultant of all people…
Don’t be. If software were easy, I wouldn’t have a job. Anything you share with me is kept in the strictest confidence.
Will you sign an NDA?
As soon as you make payment and we’ve scheduled a date, I’ll be happy to. Before then it doesn’t make sense . Sort of like scheduling a wedding day before you’ve gotten an engagement ring, ya know?
But I was hired to know how to solve these problems…
It’s not always the software that’s the problem, sometimes it’s the context. And the time when you know least about the context is when you’re first hired. Everyone reaches out for help sometimes. Your CEO has likely had a business or executive coach at one time too. It’s normal, and no one expects you to know everything you need to know to be successful. They do expect you to know how and when to ask for help, however.
Why do I need you? Why don’t I just pursue microservices, or serverless, or the cloud on my own?
If you think that will solve your problem, I’ll be over here cheering you on. Strictly speaking? you don’t need me. If you’ve been doing well up until this point, and you have the architectural experience to make the call, make it. If, however, you’re worried about the prospect of failure, or time isn’t on your side, then that’s when you want to call in someone experienced who’s entirely aligned to your success. You know, me. One reason I’m here is that there is no silver bullet architecture, it doesn’t matter if it works for Google, or Microsoft, or Contoso — what works for you depends on your team, your business situation, the culture of the company, all things that can’t be gleaned by copying the big tech companies.
How long before I see results?
I’ve designed the roadmap around getting you the biggest bang for your buck as fast as possible. That may mean taking an unusual first step that fixes the acute problem, and uses the bought time to fix the underlying problem. Let’s put up points on the board early, while we’re working to improve things for the long term.
I still have questions!
So do I, like why is Would you rather fight one-hundred duck-sized horses or fight one horse-sized duck? such a funny and accurate statement about software architecture? Oh, you meant for me. Yes, of course. Email me at firstname.lastname@example.org (original, I know). And if you’ve got an even funnier expression that relates to software, please include it!
Who are you, anyway?
As it says on the tin, I’m George Stocker (no relation to this guy), and I’ve been a software developer and architect for 18 years. I’ve led and managed teams, and I’ve worked in all sorts of software verticals and different sized companies, from startups that you could count all the staff on one hand to companies that would be their own city — and in one case a metropolis — population-wise.
I saved a particular company tens of millions of dollars by staving off a rewrite through a novel solution that was delivered months ahead of what any other approach would have been. My approach saved a contract worth tens of millions of dollars over the next four years. Subsequently, that company received a contract worth $880MM to expand that system. I can’t say the two are definitely related, but I can say it’s unlikely it would have happened if they had lost the contract.
I’ve worked on products that were big data (bigger than excel) but small user bases, and products that were large user bases (think top 4 financial website on the internet) but small amounts of data per user. And as you can probably already guess, that’s given me lots of architectural insights and contexts to try things that would work (and some that didn’t work), and I’m bringing that breadth of experience to bear. Not to bears. But to bear. Like, as a gift for you. No, the gift is not bears. That probably wouldn’t be a very good gift anyway. But architectural advice that can save your team and your product? I believe that is a very good gift indeed.
Time’s almost up!
You’re running out of web page. Do you want to keep having that sinking feeling that you’ll have to rewrite your system and it’s going to suck? No one wants to have that feeling, especially for longer than the length of a web page. Schedule a free 15 minute call now.
Still not sure? Email me at email@example.com and we can set up a time to chat.
My 100% Money-Back Guarantee: If you get a roadmap that doesn’t have a viable solution to your problems, I’ll refund your money in full.
Availability is Limited
I can only fight two horse-sized ducks a month. Roadmap scheduling is first come, first served. The sooner you apply, the sooner neither of us will have to fight your horse-sized duck ever again (and hopefully not fight 100 duck-sized horses ever, either).
You did it. You reached the end of the page. Email me and tell me so and I’ll send you a random fun fact about whatever topic I’m into that day. Today’s fun fact: If you condensed all of time (starting at the Big Bang) into one day, humans would have appeared at ll:59:33pm. Computers would have appeared at 11:59:59.667pm.