OurModule

How we work

A clear, collaborative process, from your first message to full handover.

Hiring someone to build software is uncomfortable when you cannot see what you are buying. So here is exactly how a project runs: what happens at each step, what I need from you, and what you end up holding at the end. No technical knowledge required at any point.

  • Typical length2 to 8 weeksWebsites 2 to 4, AI workflows 2 to 5, business systems 4 to 8
  • First cost to you$0The conversation and the quote are free
  • How you payBy milestoneOnly for work that is built and approved by you
  • Your contactJust meNo account manager, no hand-offs

One module at a time

It is the idea the company is named after. Instead of one giant project that only pays off at the very end, we build in modules: the most valuable piece first, live and earning its keep while the next one is built. You see a return on your investment as soon as possible, and every next step is a choice, not a commitment you made months ago.

  • Module 1live and earning
  • Module 2being built
  • Module 3when you are ready

Software people call this agile development: build a small working piece, use it for real, and let what you learn shape the next piece. You do not need to remember the term. You will just notice results arriving early and often.

The five steps

  1. Step 1: Talk and plan

    one conversation

    Everything starts with a conversation, not a contract. You tell me what is slow, frustrating, or costing you time, and I ask enough questions to understand how your business actually runs.

    • It starts with one easy conversation, over a call, email, or in person if you are local, whichever suits you.
    • I then work out what would genuinely help, and what is worth building first. Sometimes the honest answer is smaller than you expected.
    • You get a fixed quote broken into milestones, each with a plain-language description of what it delivers and when, usually within a few days.
    • If the quote works for you, we sign off and get to work. Nothing starts before your go-ahead.
    What I need from you

    A description of the problem in your own words. You do not need to know what the solution should be.

    What you get

    A fixed quote, a milestone schedule, and a clear plan you can say yes or no to. This step is always free: if I can't find you a real way to save time or money, you shouldn't pay a cent.

  2. Step 2: Build with check-ins

    1 to 6 weeks

    I build in stages so we always stay on the same page: you see the work as it comes together.

    • Before I build anything, your accounts are created under your business name: hosting, domain, email, and any others. I build inside them from day one, so there is never anything to transfer later.
    • Each milestone from the quote gets built and then shown to you as real, working software, not mockups or progress reports. A review works best when you have something to click around in, even while it is rough.
    • If something is not right, we catch it at that milestone, while it is still easy to change.
    • You always know which stage we are on and what is coming next, and the price does not move unless you ask for something new and approve the cost first.
    What I need from you

    A little time at each milestone to look at what has been built, share your thoughts, and approve it.

    What you get

    Working software at every stage, and no surprises at the end.

  3. Step 3: Review and refine

    2 to 7 days

    Before anything goes live, you get proper time with the finished build to use it the way you actually will.

    • You try the finished work on your own devices, desktop, tablet, or phone, and note anything you would like polished even further.
    • I make the final refinements.
    • Nothing goes live until you are happy with it.
    What I need from you

    A proper look at the finished build, ideally with anyone on your team who will use it every day.

    What you get

    A finished product that works the way you expected, with the rough edges taken off.

  4. Step 4: Train and launch

    1 to 5 days

    Software nobody knows how to use is not much use. If your team needs to be shown, I show them.

    • If you would like it, I walk your team through the parts they will use, on real data.
    • You get plain-language documentation explaining how everything fits together, so you are never lost and any future developer could pick it up quickly.
    • We go live together, at a time that suits your business. Nothing old gets switched off or archived until you say so.
    • I stay close for the first stretch after launch for any questions that arise.
    What I need from you

    A sense of who needs to know what, and a launch date that works around your busy periods.

    What you get

    A live website, system, or workflow, and a team that knows how to use it.

  5. Step 5: Hand over and stay available

    about 1 day

    This is the step most people never get from an agency. Everything is yours, in your name, with nothing held back.

    • On a single video call, you change the passwords and we move any two-factor authentication over to your devices together, one account at a time. From that point I can only get back in if you invite me.
    • Because the accounts were in your name from the start, there is nothing to transfer, unlock, or buy back.
    • You are free to bring in anyone else at any point, and they will find a documented system rather than a puzzle.
    • I stay available for tweaks, new features, or whole new projects whenever you need me. Anything substantial gets its own fixed quote first.
    What I need from you

    About an hour on a video call, while we hand everything over together.

    What you get

    Complete ownership, no lock-in, no required monthly retainer, and someone who already knows your setup if you want more done later.

Robert Smith at his desk
Who you'll be working with

Robert Smith

Every conversation, every build, and every handover in the five steps above is with me personally.

More about me

Common questions

  • What if I want to stop partway through?

    You can. Work is billed by milestone, so you only ever pay for what has been built and approved by you. Whatever exists at that point is yours, in your accounts, documented, and any other developer could carry it on.

  • What if I change my mind about something?

    Small changes are part of building, and check-ins exist to catch them early. If you want something genuinely new, I tell you what it costs and how it affects the schedule, and you decide. The price never moves without your yes.

  • How do we stay in touch?

    Email for most things, a call when talking is quicker, and in person if you are in London, Ontario and prefer it. You hear from me at every milestone at minimum, and I always reply within one business day. There is no account manager and no support queue: you always talk to me.

  • What do I need to prepare?

    Nothing formal. Bring the problem, and my questions will draw out the rest: what is slow, who does it today, and what better looks like. There is no paperwork to fill out and nothing to install. Just show me your process and I will handle the rest.

  • What if something breaks later?

    Tell me and I will look at it. If something I built turns out to have a fault, I fix it, and that is not billable work. Changes to outside services, changes made by others, and new requests get a fixed quote first.

  • What if I already have a website or system?

    Often we can build on it. Sometimes improving what you have is right; sometimes rebuilding is faster and cheaper. I tell you honestly which I think applies.

Avoiding the IT horror stories

Most people have heard a story about a build that went badly. Here is how this process avoids the classic pitfalls.

Ownership
The story you have heardSite or system lives in the agency's accounts; leaving means a migration or a fee.
How I workEverything in your accounts, in your name, from day one.
Pricing
The story you have heardHourly billing that creeps, or a total that grows before launch.
How I workA fixed quote by milestone; it changes only when you ask for something new.
Ongoing cost
The story you have heardA required monthly retainer or maintenance plan.
How I workNo required retainer. Running costs go straight to the providers, at cost.
Who you talk to
The story you have heardAn account manager, then a project manager, then a developer.
How I workOne person, the one building it.
Documentation
The story you have heardA login and a goodbye.
How I workPlain-language documentation, so any developer can pick it up.
Availability
The story you have heardSupport in a distant time zone, with replies days later.
How I workLondon, Ontario, on North American hours, with replies within one business day.
How things are explained
The story you have heardJargon that leaves you more confused after the meeting than before it.
How I workPlain English. Technical detail lives in your documentation, not in our meetings, unless you want it.
Strings attached
The story you have heardDiscounts that require testimonials, reviews, or referrals.
How I workThe quote is the quote. No strings.

No required monthly retainer and no lock-in. You own everything we build together, in your own accounts.

Start your projectBack to the overview

See how this runs for each kind of project: Websites · Business systems · AI workflows