Six steps from first call to live product
Every Pledge Automations project runs the same six steps, from a free 30-minute call to launch and support. The price is fixed before any build starts. You get a working version to try every week, and you own the code and accounts from day one.
- First call
- Free, 30 minutes
- Price
- Fixed, agreed before the build
- Progress
- A working build every week
- Ownership
- Your code and accounts from day one
The six steps
The same sequence whether we're automating one workflow or shipping a full app. You always know which step you're in, what it costs and what you get at the end of it.
Step 130 minutes, free
Discovery call
We listen first, then tell you honestly whether we are the right people to build it.
You walk us through the problem, the people it affects and what success would look like. We ask about the systems you already run, the constraints you can't move, and the deadline that actually matters. If we're not a fit, we say so on this call.
What you get
- A clear read on feasibility
- Rough budget and timeline range
- An honest yes or no
Step 23–5 days
Scope and proposal
A written plan with a fixed price, a dated schedule and an explicit list of what is not included.
We turn the conversation into a scoped build: the features in version one, the order we'll build them in, the integrations required, and the assumptions the estimate rests on. There is no hourly billing. You approve one number before anything starts.
What you get
- Written scope document
- Fixed price and payment schedule
- Delivery dates per milestone
Step 31–2 weeks
Design and architecture
You see the product before we build it, and sign off on how it will actually work.
Interface flows, the data model and the automation logic behind the scenes are designed together, because they constrain each other. You review clickable screens and a plain-language description of how information will move through your business.
What you get
- Interface designs
- Data and integration map
- Agreed technical approach
Step 42–12 weeks, by scope
Build in weekly cycles
Working software every week, in an environment you can open and use yourself.
Each Friday you get a link to the current build and a short note on what changed, what's next and anything that needs a decision from you. Your feedback goes straight into the following week. Nothing is saved for a big reveal at the end.
What you get
- A weekly build you can test
- Friday progress note
- One direct channel to the people building it
Step 5About a week
Launch
We ship it properly: real data, real users and monitoring in place.
Production setup, data migration, App Store and Google Play submission where relevant, and a recorded handover session for whoever joins your team later. We stay close through the first days of real use, when the genuine edge cases surface.
What you get
- Live in production
- Recorded handover and documentation
- Monitoring and alerts configured
Step 6Ongoing, optional
Support and iteration
An optional monthly retainer keeps improving what we built after launch.
The retainer covers fixes, small improvements and a standing call to decide what's worth building next. You own the code and accounts from day one, so staying with us is always a choice rather than a dependency.
What you get
- Agreed response times
- Monthly improvement cycle
- Full ownership of code and accounts
Four rules we work by
They hold on every project, from a two-week sprint to a full product build.
One senior team, start to finish
The people on the discovery call are the people who build it. Nothing is handed down to a junior bench after you sign.
Fixed price, not open-ended hours
You approve a number before work begins. If we misjudge the estimate, that is ours to absorb, not your invoice to grow.
You own everything
Code, repositories, cloud accounts and data are in your name from the first commit. No lock-in.
Automation with a person in the loop
AI handles the repetitive work; people keep approval over anything consequential. We design that boundary deliberately.
Ways to work with us
Fixed prices, agreed in writing. Product builds follow the same process we used for our own apps, including Pledge, Forge and TOGA.
Automation sprint
From 2 weeksWhere most clients start
One painful workflow automated end to end and running in your stack. The best way to start.
- One workflow, fully live
- Fixed price
- Handover and documentation
Product build
6–12 weeksA web or mobile product with AI at its core, designed, engineered and launched.
- Design and engineering
- Weekly releases
- App Store and Google Play launch
Embedded partner
MonthlyWe act as your AI and automation team, shipping against a shared roadmap.
- Rolling roadmap
- Priority support
- Cancel any month
Questions about the process
Anything else, email hellopledgeteam@gmail.com.
We take a small number of engagements each quarter, so it is usually one to three weeks from signed scope to the first build week.
One decision-maker who can answer questions within a day, access to the systems we're connecting, and an hour a week for the review call.
Yes. You approve one number in writing before any build starts. If we misjudge the estimate, we absorb the difference rather than growing your invoice.
Small changes get absorbed. Anything that materially moves the work gets a short written change note with its own price and date before we touch it.
You do, from the start. Code, repositories, cloud accounts and data are in your name from the first commit, so there is no lock-in.
No. A monthly retainer for fixes, small improvements and a standing planning call is optional. Because you own the code and accounts, staying with us is a choice, not a dependency.
Yes. With bases in Dubai, London and Melbourne we cover the working day across the Gulf, Europe and Australia.
Step one is a free 30-minute call.
Thirty minutes with the people who would build it. You leave with an honest read on feasibility and a rough budget and timeline, or a straight no. We reply within one working day.