I look at client work a little differently from most software developers
My work with you is a partnership. We are creating something that will last. To accomplish this, we need to make a plan, execute it in steps and continuously reassess whether the plan is in need of change. If changes are needed, I want us to move toward those changes without delay.
First, we'll get together over Zoom or Google Meet and talk over your project and your timeframe. We'll discuss my background and capabilities and see whether we have some synergy that will push your project forward in ways that delight us both.
You are looking for some help with a challenge and/or opportunity. I am looking for a comprehensive software solution for you that I can prepare in the most direct way possible, but that also keeps your options open for change.
Second, we will move into the Proof of Concept stage. I'll put together the NoCode tools I think we will need for your project and test that I can connect to all of the services and databases. I'll also check for contingencies and alternatives so that we can discuss their relative merits. Then, we'll meet over Zoom/Meet again to plan a balanced way forward, a budget and a timetable.
Third, I'll proceed with the work and we'll meet often to ensure the project is going well. This will continue until the project is delivered.
Keep in mind, changes are expected (see below).
Not only welcome, but expected and encouraged.
Larger projects take time to complete, even if you have a team. This means that what was wanted when a project began can become less so with time. Seemingly important tasks from the start of the project can become unnecessary, sometimes problematic, several weeks in. Other opportunities can appear. More constraints may arise. Following the original plan in light of these changes makes little business sense.
Imagine delivering a project 6 months after onset where the deliverables are all met, but the natural evolution within the company and its business has changed to an extent that the original goals are no longer valid. As a developer, I could deliver what I promised yet the client would be unhappy. This must never happen.
To this end, I ensure that the initial project is thoroughly scoped and priced, but that price is subdivided by activity (or similar) into named tasks. These scoped and priced tasks are crucial. If the client's goals change, then the pricing of those no-longer-needed tasks becomes available to be used for whatever needs to be done now. It's a simple as that.
Some clients prefer to develop their project using a learn-and-see approach. They find the initial project is very exploratory, especially at first. It does not lend itself to a detailed project scope, at least not right away. They need us both to try things and act on what we find.
I am delighted to travel this road with them. All we need to do then is set a budget and a timeframe.
Let the exploration and discovery begin!
If you've read my NoCode / LowCode page, you will have noticed that I am quite enamoured with NoCode and LowCode tools. They have come a long way. ... more on NoCode
These tools provide a vital service for freelancers and agencies: they allow us to create fully functional web and mobile apps quickly. And that gets us in front of our clients, confirming UI/UX implementation details, far more quickly than with traditional software development.
Clients are free to choose my tools and have me develop their apps in whichever way they like. However, given free rein, I will always suggest that we begin with NoCode / LowCode tools. I have selected tools that meet this need very nicely indeed. You can look forward to faster delivery and reduced costs on new projects.
... more on NoCode
I occasionally write a newsletter with insights into Coding and NoCoding, including tool reviews, and case studies. No filler. That's why it's occasional. Sign up here