Sales
Give every inquiry a next step.
Organize contacts from your forms, prepare replies or quotes for review, and follow up on each opportunity.
Inquiries · Quotes · Follow-ups
Less busywork.
More business.
We design and build custom automations for small businesses. We connect inquiries, documents and follow-ups so your team can focus on the business.
A 30-minute conversation with Adrian.
For small businesses. Wherever you do business.
We work in English and Spanish.
The work repeats.
Your effort shouldn’t have to.
We start with a task that takes up your time today. Then we design the process around your business and the tools you use.
Customers
Keep the context close at hand.
Bring customer details and documents together. Prepare answers to recurring questions and route requests that need personal attention to your team.
Information · Documents · Support
Operations
Less copying, pasting and chasing updates.
Connect records, prepare reports and notify the right person when information is missing or a task needs attention.
Records · Reports · Notifications
These are possible automations. We review feasibility and agree on the scope for your operation.
What we work with.
Automation, AI and tools for organizing work. We choose what makes sense for your project.
-
n8n
Workflows that connect your tools.
-
Claude
AI to support reading and prepare drafts.
-
Google Workspace
Email, documents and spreadsheets.
-
Notion
Information, projects and follow-up.
-
Supabase
Data for custom systems.
-
Vercel
Publishing websites and applications.
Your project does not need all of them. We review available connections, access and costs before defining the scope.
Let’s talk about your tools
Give the next step
somewhere to go.
Follow an inquiry from its arrival to a clear action for your team. You decide where human review belongs.
Following
up on an inquiryExample
01 / 04
A message comes in.
Someone fills out your form. The workflow captures the request so its context stays with it.
Website form
Request received
Ana · Service business
Hi, I’d like a quote for maintenance at my shop. What information do you need?
Received · Ready to organize
02 / 04
The information finds its place.
The details become a record your team can consult. There is a clear starting point for the next conversation.
Customer record
Contact record
Ana · Maintenance request
- Name
- Ana
- Interest
- Shop maintenance
- Source
- Website form
- Next step
- Review the request
Organized · Waiting for review
03 / 04
The judgment stays with you.
The workflow prepares a draft. Your team reviews the response and fills in any gaps before authorizing delivery.
Draft, not sent
Response for review
To: Ana
Hi, Ana. We’d be happy to review what you need. Could you share the size of the shop and the type of maintenance? That will help us prepare a proposal.
Requires human approval
04 / 04
There is a clear way forward.
After approval, the response is sent and follow-up is prepared under the agreed rules. The team can see where things stand.
After approval
Next step defined
Owner: sales team
- Response
- Sent with approval
- Next action
- Wait for shop details
- If there is no reply
- Reminder at the agreed interval
Follow-up prepared
Select a step to explore the process.
Illustrative demonstration · Fictional data
This scene explains a possible process. The final system is built around your company’s tools and rules.
Understand the work first.
Then connect it.
One well-chosen task is a better starting point than trying to automate the whole company at once.
-
Talk it through
In 30 minutes, we review what repeats, where work gets stuck and what is worth solving first.
-
Agree on the scope
Get a proposal with a defined scope, price and timeline. We also clarify what your team needs to contribute.
-
Build and test
We connect the workflow and review it with you. We test the normal path and what should happen when something is missing or fails.
-
Put you in control
Your team learns to use the system. We agree on how changes, monitoring and ongoing support will be handled.
The handoff is
more than a link.
Delivery includes what your team needs to understand the system and keep it running.
-
The system and access
Built inside your accounts. You keep control of your tools and the work delivered.
-
The documentation
A guide to the process, its connections and the steps to operate it.
-
Team training
We walk your team through the system before handoff.
-
A support agreement
We define support coverage, who handles alerts and how changes will be managed.
A direct relationship.
With the person building it.
Adrian CappellaFounder of Cappflow
I’m Adrian. Before building automations for other companies, I needed them for my own. My background is in civil engineering: I care about systems that solve everyday work.
At Cappflow, we start by understanding how your business operates. The tools follow the problem.
Let’s talk about your businessBefore we start.
The questions worth answering before we connect the first tool.
Is my business too small?
We work with small businesses. The starting point is a recurring task with clear steps that takes up time. In the initial conversation, we review whether automating it makes sense.
What should I automate first?
An inquiry that needs follow-up, information you copy between tools, or documents you need to collect. Together, we choose a focused process and define how to check that it works.
What does it cost?
It depends on the process, integrations and support. After understanding the work, we prepare a proposal with a defined scope and price.
How long does it take?
It depends on scope. We confirm the timeline in the proposal and distinguish the first version from full delivery, including testing and training.
Do I need to change my tools?
We first review what you already use and which connections those tools allow. If a change or additional subscription is needed, we include it in the proposal before building.
What do you need from my team and me?
An explanation of how you do the task today, suitable examples for testing, and someone to review the process. Required access is defined according to scope.
Who owns the system?
You do. We build inside your accounts. The system and documentation stay with your company; external tools retain their own licensing terms.
What happens if something fails?
We design error handling and alerts as part of the workflow. Monitoring and ongoing support coverage are agreed before handoff.
Does AI make decisions for my team?
We define which actions can be automated and which require approval. When a response or decision needs judgment, the process should involve a person.
Your next improvement
can start with one task.
Tell us what is taking up your time. In a 30-minute conversation, we review the process and what a useful next step could be.