Part 1 of 4 · The problem
Most of your day is micro-tasks.
Retyping, chasing, checking, confirming. None of it pays, and all of it adds up. Here's one service request, the way it usually goes. Tap and watch what changes.
One service request, today
8 steps- 01Customer calls; you write it on whatever's nearby
- 02Open the app (it wants an update first)
- 03Find the right form
- 04Re-type the customer's name and address
- 05Take photos, then email them separately
- 06Copy it all into the spreadsheet
- 07Text the office that it's done
- 08Wait for someone to confirm
Try it. This is what a one tap request feels like.
Now stretch that across a whole day.
Before
A sales rep's Tuesday
- A pocket full of business cards from yesterday, each one typed in by hand.
- Tonight's route planned by guesswork on a map.
- Somebody who was due for a visit gets missed.
- Visits written down after the fact, if there's time.
After
The same Tuesday
- One photo of the cards. They become customers, and duplicates get flagged.
- Pick the day. The stops come back in order, around the 10:30 appointment.
- Everyone due this week is already on the list.
- Pull up to a stop and the visit is marked from the phone's location.
Illustration built from Sales Mapper, a tool in daily use. Same rep, same customers; the micro-tasks happen on their own and he reviews the day.
Part 2 of 4 · My approach
Stop living in the white noise.
I don't start with what you asked for. I go upstream, to where the work starts.
Philosophy
Go to the source
Before I design a screen, I follow the work from the first phone call to the money in the bank.
Methodology
Find the waste
- Where can it be automated?
- Where does bad information get in?
- Where is work typed twice?
- Where is someone starting what a system could start?
Technique
Confirm, don't initiate
The system does the work and hands it to your people to review and confirm. No app noise, no patches, no upkeep on their end. One tap.
Your team confirms; the system does the work
Why a builder
Built by someone who has built things.
I ran a commercial door company for years: the warehouse, an aluminum fabrication shop and the field crews. Construction taught me that you survey before you build, you never skip a phase, and you hand the owner something they can run. I build software the same way. My company is DBC, Digital Builder Contractor; One Tap Request is the name on everything I build.
— Daniel Kaupie, founder
- ConstructionPresident and CEO, R&A Supply & Install. Moved the warehouse from 5,000 to 13,000 sq ft without stopping service.
- FabricationRan an in-house shop building aluminum door frames, sidelights and windows.
- InventionsPatent filings on precision templates and tools for field installers.
- ServiceU.S. Army veteran, Patriot PAC-3 system.
- CommunityHabitat for Humanity, Monterey County: board member and vice president, 1,000+ volunteer hours. Scoutmaster, 2014–2018.
How I build: the DBC Build Method
Built like a building. Improved like a factory floor.
I run every phase myself. No subs, no finger-pointing. Each phase ends with something you can hold, and the job doesn't stop at the keys: every process gets measured, refined and tested again until it pays for itself.
Kaizen: it keeps going after handoff
- Every process is measured once real people use it.
- What's slow or error-prone gets refined, then tested again.
- The loop repeats until the result is accurate and the time it saves is real.
Part 3 of 4 · The proof
Don't take my word for it. Take theirs.
In their words
Then watch the work itself.
Every project below is a real build. What you see here are demos with sample data, so no client's actual app, data or branding is shown.
Tap Watch it work on any project: one tap, then watch what the system does for you. About ten seconds each. Every preview is a privacy-safe sample with its own look, because no two builds look alike.
Investor or partner? Several of these are built to grow past one customer. Let's talk →
Part 4 of 4 · Your first step
What you get, what it costs, how we start.
Nothing to download. Nothing to babysit.
Phone, tablet or computer. Open the link and it works. No app store, no installs, no "please update" screen in front of a customer.
No app store to wait on. Everyone gets the improvement the next time they open it.
No license fees for using your own tool. You get the keys, the accounts and the manuals at handoff.
Every change is built and checked on a separate test copy before it touches the version your team uses.
How pricing works
You pay once for the build and you own it. Hosting and outside services have small monthly costs, listed line by line in your spec book before you commit. No license fees to me.
Common questions
Do my people have to download anything?
No. Everything runs in the web browser on any phone, tablet or computer. You can still add it to a phone's home screen so it opens like an app.
Is this just another subscription?
No. You pay for the build and you own it. The care plan covers hosting, updates and support, and it's optional.
What happens if you're not around?
You own the code and the accounts. At handoff you get the as-built documents, an admin guide and training, the same way a building owner gets the manuals and the keys.
How long does a build take?
It depends on scope. You get a phased schedule with the proposal, and each phase ends with something you can review before the next one starts.
Can it work with the tools we already use?
Usually, yes. Existing tools, data and accounts are checked during the site survey, and the plan says what connects, what gets replaced and what stays.
Will you plan for things wearing out?
Yes. Like any building, software ages: services change prices, connections get retired. Every handoff includes a replacement schedule so you're never surprised.
So, in short
- The problem. Your day is full of micro-tasks that pull you away from the work that pays.
- My approach. I go upstream, find the waste, and build a system that finishes those tasks, so you only review and confirm. Then I keep measuring and improving it.
- The proof. Real builds in daily use, like the route planner a sales rep opens every morning.
- Your first step. Tell me one task that eats your day.
Tell me one task that eats your day.
Three quick taps about how work reaches you, then tell me the task. I read every one myself, and the walkthrough is free.
Also from One Tap Request · free business cards
Stop buying paper cards. Let your customers pass you around.
Build a digital business card on your phone in a few minutes, free for good. Your customers keep it in their texts and forward it to the people they run into every day. Word of mouth, with a request button attached.
- Forwarded, not filed. Paper gets handed out once. A link gets sent to a neighbor, a coworker, a group chat.
- Every copy can book a job. Whoever opens it can tap to call, text or send you a request with the details filled in.
- Never runs out, never goes stale. Change your prices or hours once and every copy out there shows it.
- Not an app. Nothing for you or your customers to download, no account to create. It's a link.
It works on our own business. When our ride service's regulars got the card link instead of a phone number, it brought in 11 new customers in 7 days, from riders forwarding it. People trust a recommendation from someone they know more than any ad: 89% said so in Nielsen's 2021 Trust in Advertising report.
How one card spreads