You have an idea for a software project. You’ve noticed an opportunity to create a new tool or platform that will help you increase customer engagement and reach new markets. But once you have a goal in mind, you have to walk through a minefield to get there. Two out of three software projects don’t succeed1. How can you avoid a similar fate?
You Need The Right Help.
You have to decide how you are going to build this thing. And you have to figure out who is going to do it. If you happen to be a high-tech company that has plenty of engineers with the skill set you need to deliver, and they have the time, and you can afford the additional resources, then you are set. But what if you don’t have a specialist in-house?
You could hire someone, but hiring is expensive and time-consuming. If you have technical expertise, you can vet developers, but if you don’t, how can you be sure you won’t hire a dud? Then once you find someone, there’s healthcare, equipment, scheduling, taxes, and a whole mess of overhead. You have enough headaches as it is and don’t need to add all of this on to your plate.
You could outsource the work overseas, But this is highly risky. It’s cheap, sure, but you end up working with people using a different language on a different time table. Projects live and die on communication.
You could hire a large agency, and pay for a lot of overhead. Working with large teams is like riding an elephant to work: It’ll get you there eventually, but it’ll move slow and probably have left a lot of unexpected expenses in its path.
So, you need someone that can deliver … while reducing complexity in your business instead of increasing it.
You need someone that understands you and your business … and can answer emails in a timely fashion.
You need someone that has the reliability of a large company … but the nimbleness of a small one.
Hi, I’m Glenn! And I’m…
I’m 100% Focused on Your Project’s Success
I’ve built my services from the ground up, aimed at helping my you achieve your objectives. I’ve worked in the industry for seven years and seen my share (and been a part of) of failed software projects. Why do so many projects fail?
- Lack of knowledge. Developers don’t know what they are building or more importantly why it’s getting built.
- Going over time and over budget. If you don’t know what you are doing, how can you plan effectively? Answer: You can’t.
- Lack of constraints. There’s always one more thing to do, and you can kill a project by over-watering it with feature ideas.
- Lack of direction. Every week the team sprints in every direction but forward. After enough iterations through the deserts, projects die of dehydration.
All of these share a common cause.
- People fear the unknown, so they avoid it entirely.
- People fear loss, so they can’t make the hard decisions that help their project.
- People fear criticism, so they don’t talk to their customers enough.
- People fear failure, so they push back the launch until it’s “perfect”.
So how do you beat the fear? Hard work and research. It’s not sexy, but it works.
But Aren’t You Just Some Coder?
I’ve written a lot of code. If we work together, I’ll write some more. But I’ll let you in on a little secret.
The code is the least important part of a software project.
I know, it sounds weird, but let me explain. Software is communication. It’s communication between the people who own it, the people who built it, and the people who use it. My goal isn’t to only create the tool, but to teach you and your customers how to be better through the tool.
I don’t work with clients unless I’m sure my work is going to have an impact. I figure out your goals, how we’ll measure success, then do research and planning to find the most effective way to get from where you are to where you want to be.
I plan on being an investment, not an expense.
Then I’ll get into the “coding stuff”.
Glenn brings solid ideas to the table time and time again. As a result, I rely on him daily to deliver practical solutions for our clients and work server side magic for my front end designs. I learn something every time we talk!”
Zach AligProof Industries
So How Do I Know You’ll Be On Time and Within Budget?
The most dangerous part of web development tools and “agile” project management practices available these days is that they let people start working before they know what the hell they are doing.
Before we work together, we’ll talk about the goals you are trying to achieve and how we’ll measure the success of the project. Once we’ve done that we’ll agree on a fee that works for both of us. You know what to expect at a certain price. Your project is 100% guaranteed to stay within budget. Heck, I wrote the book on it.2
We needed a great Angular specialist with a focus on test-supported code to help our in-house team. Glenn was able to step in and translate complex requirements into a seamless interface for us.
Jill AdamsSenior Project Manager
Building software is just step one. Once we reach the goal of an initial project, we can go down a few paths.
- All of my work comes with e 30-day guarantee. If a defect slips through all of the automated testing and user acceptance, I’ll fix it.
- After project completion, I can provide training to make sure you know how to get the most out of your product.
- And if you want to learn continually and grow your business, we can work out a fixed monthly retainer including monthly meetings, priority phone and email support, and on-going, growth-driven development.
- Or maybe we do another a one-off project. A project is a set of defined work with an objective; One piece of software can involve many projects.
Glenn understands my evolving business development needs, and has more than once provided helpful consultation related to marketing and customer discovery, pricing, and competitor analysis. In his consultations, I have found in him a trusted partner and someone who’s made my life as a CEO easier.