- Do you really meet in person?
- Yes, and I think it's usually worth doing at least once. It's a lot faster to understand a business in person than over a call, especially when the current process involves paper, a whiteboard, or a very specific spreadsheet. After that, most projects run fine over calls and email.
- Do you only work with Connecticut businesses?
- No. A lot of my work is out of state and always has been. Connecticut businesses just have the option of a developer who can drive to them, which matters to some people and not at all to others.
- Is a local developer more expensive than going offshore?
- The hourly rate usually is. I think the total often isn't, though, because offshore projects tend to lose their savings to rework, misunderstood requirements, and the time it takes to manage it all. I'd rather scope the project honestly and give you a price before I start, so you can compare real totals instead of hourly rates.
- How small is too small?
- There isn't really a minimum. Some of the most useful projects are small, like one automation that saves an hour of retyping every morning or a report that doesn't have to be rebuilt by hand each month. And if it turns out you don't need anything built, I'll tell you that.
- Can you work with the systems we already have?
- Yes, that's most of the work. Very little of it starts from nothing. Usually it's connecting the platforms you already pay for, pulling your numbers into one place, or replacing a spreadsheet the business has come to depend on. You keep what works and I build what's missing.
- Who owns what you build?
- You do, once the project is paid for. That includes the source code, accounts, infrastructure, and documentation. I don't hold anything back to keep you on a retainer, so if you ever want to hire someone else, they'll have everything they need.