What goes into the price

A useful estimate explains the work, the assumptions and the costs you’ll have after launch. Here’s what we look at before putting a number on your project.

01

Scope and features

The number of pages or screens is only part of the work. Accounts, permissions, bookings, payments, search and reporting each add behavior that needs to be designed, built and checked. A small site with a few clear actions is a different project from an application with several types of users.

02

Design and content

An existing design and ready-to-use text can reduce the work. A new visual direction, custom layouts, illustrations, copy or a large amount of content adds time. We’ll identify what you’ll provide and what needs to be created before estimating it.

03

Data and integrations

Connecting to payment services, calendars, business software or AI models involves more than adding a button. The work can include handling permissions, moving existing records, mapping fields, protecting information and making failures understandable to the user.

04

Technical complexity

A familiar website feature is easier to estimate than a new tool, a hardware integration or an experimental simulation. Where there are unanswered technical questions, a small discovery or prototype phase can establish what is feasible before pricing a larger build.

05

Testing and launch

The price needs to account for the actual ways people use the product: phones, computers, different accounts, incomplete forms and unexpected errors. Launch work may include deployment, domain setup, configuration, documentation and checking the live version.

06

Timeline and coordination

A realistic schedule depends on the scope, feedback and any outside services or hardware. A tight deadline, multiple reviewers or work that must fit around an existing system can change how a project is planned. We’ll discuss those constraints before committing to a date.

07

Support and future changes

Fixing an issue in the agreed work and adding a new feature are different requests. The quote should explain what support is included, how later changes are handled and whether ongoing maintenance is part of the arrangement.

08

Running costs

Hosting, domains, email, storage, paid APIs and AI usage may have continuing costs outside the development price. These depend on your providers and usage. We’ll identify the expected services, who owns the accounts and which charges you pay directly.

The written quote

What you should expect to see

The scope and deliverables, what is excluded, estimated timing, payment milestones, outside costs and the support included. Ownership, handover and any dependencies should be clear before development starts.

If the plan changes

New ideas often come up during a build. We’ll discuss the effect on price and timing and agree on the change before doing additional work. Larger projects can be split into phases so you can review a working result before deciding what comes next.

To help me estimate your project

Tell me who will use it, the main things it needs to do, what already exists, any deadline and a budget range if you have one. Screenshots, sketches and examples of similar products are welcome.

Experience

Custom software and hardware

I have extensive hands-on experience building custom software and hardware.

Hardware and design

Custom-built drones, computer builds, CAD design, 3D-printed parts and robotics.

Software

Websites, web and mobile apps, desktop software, custom programs and tools, AI, AI tools, AI integration, workflow automation, business systems, simulations and general programming.

Your next project

Let’s build your ideas.

Tell me what you want to make, what it needs to do and where you’re starting.