How we work
We build it with you, then stay beside you until you don’t need us.
Promptwise AI builds Promptwise OS, the AI operating system we run our own business on, for B2B SaaS founders: one module, one area or the whole thing, around the tools you already use, then stays on as part of your team. Adam Agresta leads every build and stays your main contact from the first call to the day the training wheels come off.
Example
Pipeline build
- Discover
- Scope
- Build
- Hand over
Latest note · Tuesday call
Instant reply is live on demo requests. Follow-up rules agreed with your team. Next up: your live pipeline view.
Working together
Most AI projects fail after the build, when nobody is there to answer questions or fix what breaks. So the support is the point, not an extra.
A plan that fits your business
We start from how your business actually runs: your sales cycle, your team, your busy months. Then we agree the order of work, starting with whatever saves the most time or wins the most deals first.
Meet as often as you need
Weekly while we build, then fortnightly, monthly or only when something comes up. Some founders want a standing call, others want to be left alone until there is something to see. Both work.
One channel, quick answers
We set up a shared Slack or WhatsApp channel, whichever your team already lives in. Questions get a reply the same business day, from Adam, not a ticket queue.
Your own project page
A private, password-protected page just for your build. It shows where things are at, the timeline, what we have learned about your setup, every decision and meeting note, and a feedback box that goes straight to Adam.
Training wheels on
Nothing is switched on and left. New automations run beside your current process until they match your standard, your team is shown how each part works, and every part comes with a plain-English how-to.
Keep us on your way
Once it is running you choose how much help you want: one or two meetings a month on a consulting or contractor basis, or a retainer where we join your team and keep improving the system. Agreed up front, and you can stop any time.
Our standard
On every engagement
Six things that come with every build, big or small. They are how we keep your business running while we change it.
Notes after every meeting
Notes and next steps after every meeting, posted to your project page.
Progress in plain English
Plain-English progress on your project page, as often as you want it: what is working, what is leaking and what we are doing next.
Tested before it goes live
Every change tested on a copy first, then switched on at a quiet time, never in the middle of your working day.
Easy to roll back
Anything can be rolled back to how it was, usually in minutes.
A person signs off
A person signs off anything that goes to your customers until you are happy for it to run on its own.
A 24-hour heads-up
If anything ever goes wrong, you hear from Adam within 24 hours with what happened and the fix.
Training wheels on, then off
We start hands-on and step back as your team takes over. Tap or drag through the stages to see what happens when.
Week 1
We do the heavy lifting
Weekly calls, and Adam builds and runs everything while your team watches how it works.
Illustrative. Every business moves at its own pace, and you decide when the training wheels come off.
The Funnel Health Check
Answer around 12 quick questions and get a score for six stages of your funnel, with your biggest leak and your top three leaks on screen straight away. No email needed.
If you like what you see, book a free 30-minute walkthrough. We look at where your leads really go today and agree the first thing worth fixing.
How a build comes together
Founding builds are small, scoped projects of up to 4 hours. Bigger builds are done in stages, with something working at the end of each one.
- 1
Discover
We walk through how your business runs today, screen by screen, and record it with your permission. You get our read of it to correct.
- 2
Scope and agree
What we build first, where it runs, the accounts it needs and every running cost, line by line. Nothing is bought until you say yes.
- 3
Set up, in your name
We set up the accounts and the computer it runs on together, in one short session, all owned by you.
- 4
Build side by side
Each automation runs next to your current way of doing things until it matches your standard. Then it takes over.
- 5
Widen, then hand over
Each next step goes live once it passes your checks. When you are ready, the training wheels come off.
What goes into a build
A good AI system is more than a clever prompt. It needs somewhere safe to run, clean connections to your data, and the plumbing that keeps it working at 2am.
Where it runs
Your systems
What it gives you
For most pipeline builds, the system lives inside your existing CRM, inbox and calendar, with small automations connecting them. Nothing new to buy and nothing to maintain on site.
Best for: lead replies, routing, follow-up and weekly reporting.
When a build does heavy AI work or handles data that should never leave the building, it runs on a small, dedicated computer such as a Mac mini. It is quiet, uses very little power, runs around the clock, and you own it outright.
Best for: video, documents, large data sets and sensitive information.
When your team is spread out, or a big one-off job needs more power, it runs on a server in a cloud account in your name. You pay only for what it uses, and data is deleted when a one-off job is done.
Best for: remote teams and big batch jobs.
We recommend the right setup for you, and cost it, before anything is bought.
The parts every build needs
Connecting your data
Your CRM, forms, inbox, calendar, spreadsheets and databases, joined up so nothing gets copied by hand. We use official connections where a tool offers them, and start read-only: we look before we change anything, and only write where you have said yes.
The AI itself
Business-grade AI accounts in your name, whose terms say your data is not used to train their models. The system gets its own connection with a spending limit you set, so there are never surprise bills.
The code and its history
Everything we build is kept in a private code repository that you own, with every change recorded. Nothing is ever lost, and you keep the full history whatever happens.
Logins and access
Every login sits in a shared password vault, so passwords never go by email or chat. Everyone gets their own named login with two-step sign-in, and you can switch any access off in one click.
Backups and monitoring
Encrypted backups, kept on site and offsite, with a tested plan to restore everything if a machine fails. Alerts tell us about a problem before you notice it.
Checks and guardrails
Every outside tool passes a security check before it is used. AI answers are checked against your own data, every action is logged, and nothing can move money or contact customers without the rules you set.
You own all of it
Every account is in your name, the code and documentation are yours, and Adam is a named user you can remove at any time. If we ever part ways, you keep everything running.
What we need from you
- A yes on the plan and the running costs, once you have seen them.
- Access to the systems the build connects to, read-only to start.
- Someone on your team to approve the AI’s work while it is learning.
- About an hour a week of your time while we build.
Your first module, free.
Your first Promptwise OS module, scoped at up to 4 hours of build time (worth up to A$1,000), at no cost, for B2B SaaS founders who qualify, in exchange for a case study and a video testimonial. You give us access to the tools the build needs and about an hour of founder time, and we agree the scope in writing first. You keep everything we build. Conditions apply.
Why not do it yourself?
You could. It means choosing where it runs, connecting four or five tools safely, writing the rules, testing it against real leads and fixing it when something changes, on top of selling. Most founders mean to and never get to it, or build it once and watch it quietly break. We build it in weeks, sit beside your team while it beds in, and stay on call after, so you get your evenings back.
Frequently asked questions
How often will we meet?
As often as suits you. Usually weekly while we build, then fortnightly, monthly or only when something comes up. Between meetings you have a shared Slack or WhatsApp channel and your private project page.
What is the project page?
A private, password-protected page just for your build. It shows progress, the timeline, every decision and meeting note, and has a feedback box that goes straight to Adam. It updates as we go.
Where does the system run?
It depends on the build. Most pipeline builds live inside the tools you already pay for. Heavier AI work, or data that should stay in your building, runs on a small dedicated computer in your office such as a Mac mini. Spread-out teams or big one-off jobs can use a private cloud server in your name. We recommend one and cost it before anything is bought.
Who owns what you build?
You do. Every account is in your name, and the code, its full history and the documentation are yours. Adam is a named user you can remove at any time.
How do you charge after the build?
Your choice. An hourly rate for help when you need it, or a monthly retainer where we look after the system, keep you updated and keep improving it. It is agreed in writing before we start, and you can stop any time.
What does a founding build include?
One scoped project of up to 4 hours of build time, worth up to A$1,000, agreed in writing on a free 30-minute call. We build it, hand it over and show your team how it works. In exchange you give us a case study and a video testimonial. Bigger projects are quoted the usual way.
Is my data safe?
We only connect what the build needs, start read-only, and use business AI accounts whose terms say your data is not used for training. Every login is named, every access can be switched off by you in one click, and a person signs off anything that goes to a customer.