Example package
Internal tool
One web app that replaces the spreadsheet your team runs on.
You get
- Written scope and milestones
- Sign-in and roles
- Your data moved in
- Code and docs
How it works
- 1You describe it
- 2A written scope
- 3Milestones you review
- 4Handover and a 30-day fix window
How we work, step by step · The 30-day fix window in our agreement (section 9)
Sound familiar?
What we hear from businesses before a project like this starts.
- We pay for five subscriptions and still run the business from a spreadsheet.
- No off-the-shelf tool fits the way we actually quote, schedule or bill.
- A developer left halfway through and we can't make sense of the code.
- We have a SaaS idea and need a first version real customers can use.
- Our clients email us for updates that a portal could show them.
- Every quote we got came with a 20-field form and a sales call before a single answer.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
Internal tools
Quoting, scheduling, job tracking or approvals in one web app your team signs in to.
02
Client portals
A secure place for clients to see status, documents and invoices, and send requests.
03
A SaaS first version
Sign-up, billing, the core feature and an admin view, built to grow.
04
Taking over a project
An existing codebase reviewed, stabilised and documented, then built on.
05
Integrations
Your app connected to your CRM, accounting, payments and email.
06
Hosting you control
Deployed to your own cloud account, with backups and monitoring.
Tools that come up most: Python, Django, FastAPI, Node.js, TypeScript, React, Next.js, Laravel, PostgreSQL, MySQL, Supabase, Firebase, Stripe, AWS, Google Cloud, Azure, Docker, GitHub.
What you get
Concrete pieces, each one something you can open and check when it's done.
The application
Screens, data and permissions built to the written scope, milestone by milestone.
React or Next.js, Python or Node.jsDatabase and API
A clear data model and an API other tools can use.
PostgreSQL, REST or GraphQLIntegrations
Your CRM, accounting, payments and email connected.
Stripe, QuickBooks, HubSpot, GmailDeployment
Hosting in your cloud account with backups, monitoring and error alerts.
AWS, Google Cloud, Azure, DockerHandover
Source code, documentation and a walkthrough for the next developer.
Your GitHub or GitLabTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Client portal
A portal your clients sign in to for status, files and invoices.
You get
- Client accounts
- Documents and updates
- Notifications
- Hosted in your account
Example package
Project rescue
An unfinished or unstable app reviewed and brought back under control.
You get
- Code review report
- Stabilised build
- Documentation
- A plan for what's next
How we approach it
The habits that keep this kind of project from going wrong.
1
Milestones you can open
You use each part as it's built, not a slide deck.
2
You own it
The code, the hosting accounts and the data are yours from day one.
3
A short brief to start
Tell us what you need in a few lines; the scope comes next.
How we work
You describe it. We write it down, build it, and hand it over.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- Number of screens and user roles
- Systems to connect
- Data to move in
- Hosting and security needs
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, based in Massachusetts. See example builds.
Questions people ask first
Who owns the code?
You do. It lives in your repository and your cloud accounts from the start.
Can you take over an app another developer started?
Yes. We review the code first, write down what we find, and agree a plan with you before changing anything.
Do you build SaaS products?
Yes, from the first version with sign-up, billing and the core feature, through to later releases.
Build or buy?
If an off-the-shelf tool fits, we will say so. Custom software makes sense when the way you work is part of what makes you different.
What happens after handover?
For 30 days we repair anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way and agreed with you before we start.
Do it once, we automate it. Show us the job one time and it runs on its own after that, in the tools you already use. Not sure where to start? Start with an Automation Audit.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com