01
Workflow Map
Every repeated process in your business. Who does it, how long it takes, what systems it touches, and where it sits waiting.
AI · Automation · Custom Systems
I spend 10 days inside your operation and hand you a costed plan for exactly what to automate, what to build, and what to leave alone. Then we build it.
Systems built for private lending, field service, food service, and marketing operations.
Start here
The Workflow Teardown
$2,000 flat · 10 business days · Credited in full
Book a Workflow TeardownIf I don't find three things worth doing, you don't pay.
The industries don't repeat. The bottlenecks always do.
We've built the operating systems behind a private lending firm, a field service crew, a coffee house, and a marketing agency. Four industries with nothing in common except the same three problems: work that gets done twice, tools that don't talk, and one person who's the bottleneck for everything.
Private LendingField ServiceFood ServiceMarketing Ops
Sound familiar?
The problem usually isn't that you need AI. It's that nobody can tell you where it goes.
You've read the articles. You've watched a competitor announce something. Maybe you've even bought a tool or two that's sitting in a tab nobody opens.
What you haven't gotten is a straight answer about your business specifically.
- Your team enters the same information into two or three different systems.
- Your CRM, your scheduler, and your accounting software each know a different version of the truth.
- You're paying for software nobody uses because it was supposed to fix something and never got set up properly.
- One person knows how everything actually works, and when they're out, things stop.
- Someone told you to use AI. Nobody told you for what.
None of that gets fixed by buying another tool. It gets fixed by someone actually looking at how the work moves through your business.
What makes this different
Most of what's being sold as AI right now shouldn't be AI.
Part of what you're paying me for is to tell you which is which, including the times when the answer is that you don't need us to build anything at all.
A lot of it should be a plain automation. Some of it should be a database. Some of it is a broken handoff between two people that no software will fix.
I can say that because I'm not reselling anybody's platform. I don't get a commission on the tools I recommend. We make money when the thing we build actually works, which means I have no reason to sell you something that won't.
Start here
The Workflow Teardown
A 10-day teardown of how your business actually runs, ending with a costed plan for what to automate, what to build with AI, and what to leave alone.
$2,000 flat10 business daysCredited in full toward your build
You'll finish knowing exactly which parts of your operation should be automated, which need custom software, which are real candidates for AI, and which should be left exactly as they are. With costs and payback for each one.
Whether you hire us to build it is a separate decision. The plan is yours either way.
Five things land on your desk on day 10.
02
The Three-Bucket Split
Every opportunity sorted into automate it, build it, or leave it alone. This is the part most people have never had done honestly.
03
Tool and Data Reality Check
What you're already paying for, what overlaps, what's paid for and unused, and what data is trapped where. Most AI problems turn out to be data access problems in disguise.
04
Ranked Opportunity List
Scored by impact, effort, and risk. Each one costed, each one with a payback estimate.
05
Build Roadmap
Phase one scoped, priced, and timelined. Phases two and three sketched, so you can see where this goes.
Here's exactly what happens.
- Day 1Kickoff call, 60 minutes. I request access. We schedule your team.
- Days 2 to 3I go through your existing tools and data flows. Read-only. Nothing gets touched.
- Days 4 to 6Up to four interviews with your people, 45 minutes each. Plus two process walkthroughs where I watch the work actually get done on a screen share. This is where the real findings come from, not the interviews.
- Days 7 to 8Mapping, analysis, and scoring.
- Days 9 to 10Deliverable drafted, then a 90-minute walkthrough call where I take you through all of it.
- AfterOne round of revisions within seven days. Then it's yours.
The 10 days start at kickoff and depend on your team being available in the first three days. If access or scheduling slips, the clock pauses. I'd rather tell you that now than miss a date later.
If I don't find three things worth doing, you don't pay.
Specifically: if the Teardown doesn't surface at least three implementable opportunities with a payback period under 12 months, you owe us nothing.
We've never seen a business with more than eight people that didn't have at least three. But you shouldn't have to take our word for that before you've paid us.
This is built for a specific kind of business.
A good fit if
- You're a service business or in real estate, with 8 or more people
- At least one person on your team spends most of their week on repetitive process work
- You have real volume: jobs, files, transactions, appointments
- You've tried to fix this before and it didn't stick
Not a fit if
- You're under five people. There isn't enough repetition yet to pay back a build.
- You want a chatbot on your website. That's not what this is.
- You already know exactly what you want built. Skip the Teardown and just tell me what it is.
I'd rather tell you no now than take $2,000 and hand you a plan you can't act on.
Things we've actually built.
Private Lending — Loan Condition Review
A lending firm was reviewing appraisal documents against loan conditions by hand, one file at a time. We built a system that reads the document, checks it against the conditions, flags exceptions, and clears the rest with an audit trail. Review time per file went from roughly 45 minutes to 8. Across 120 files a month, that's 74 hours back.
Case 1Private Lending — Loan Origination Platform
Same firm. The whole operation ran on spreadsheets, email threads, and shared drives. We built their loan origination system from scratch, including a guideline compliance layer that checks files against lender requirements before they reach an underwriter.
Case 2Field Service — Dryer Vent Cleaning
A field service company was scheduling, dispatching, and following up manually. We built the app the crew runs on: jobs, scheduling, customer notifications, and the follow-up that used to get forgotten.
Case 3Food Service — Juu Roku Coffee House
I own this one, which means I felt the problem before we built for it. A point of sale system built for how the shop actually runs, not how a generic POS assumes it runs.
Case 4Marketing Operations — Agency Client Systems
CRM foundations, pipelines, automated follow-up, affiliate management, and client portals for a marketing agency's client roster. The back end that makes the front end work.
Case 5
You work with me. Not an account manager.
I'm Dan Iman. I run i41 Digital.
There's no handoff to an account manager after the sales call. I run your Teardown and stay your point of contact. The team builds from that plan, which is why the roadmap stays realistic in the first place.
I'm self-taught, which I mention because it explains how I work. I learned this by building things that had to run in production for real businesses with real money moving through them, not by learning frameworks in the abstract. When I tell you something will take three weeks, that estimate comes from having been wrong about it before.
I work remotely with US clients from the Philippines. That's been the arrangement for years and it's why I can do this work at a price a mid-sized business can justify.
GoHighLevel systems, custom web applications, AI orchestration, automation architecture, and the unglamorous integration work in between.
The Teardown is the start, not the whole thing.
Build
Once we know what's worth doing, we build it. Fixed scope, fixed price, fixed timeline, all of it drawn from the roadmap you already have in your hands. Nothing gets scoped in the dark. Your Teardown fee comes off the price.
Operate
After a build ships, some clients keep us on to run it, improve it, and take on the next phase. Monthly, with a defined hour ceiling, defined response times, and 30 days notice either direction. No 12-month lock-ins.
Both are quoted against your situation, so there's no price list here. The Teardown tells us what the number is before you commit to anything.
Already know what you need?
Then skip the Teardown. Tell me what it is and we'll quote it.
Automation Sprint — one workflow, one week, doneLanding pages and websitesFunnel buildsCRM and pipeline buildoutEmail infrastructure setup
Projects typically start around $1,500 and scale with scope.
FAQ
Why would I pay for an assessment? Other people do them free.
Because a free assessment is a sales call, and you'd treat it like one. Paid means you give me real access and pull real numbers, and I give you a plan you'd act on whether or not you hire us for the build. It's also credited back in full if we do build, so if we work together it costs you nothing.
Can't I just ask ChatGPT this?
It'll give you a competent list of generic AI use cases. What it won't do is sit with your processor for 45 minutes and discover that your CRM and your scheduler don't share a customer ID, which is why three of the five ideas on that list won't work in your business.
We already know what we want built.
Then don't buy a Teardown. Tell me what it is and we'll quote the build directly.
$2,000 is a lot for a document.
It's credited in full against the build. And if the honest answer is that nothing here is worth doing, you've just saved yourself a $15,000 mistake for $2,000.
What if the plan says we don't need AI?
Then that's what the plan says. That happens, and it's a legitimate outcome. You'd walk away knowing where your actual bottleneck is, which is worth more than an AI project that solves nothing.
Who owns what you build?
You do. Code, systems, documentation, all of it. We don't hold your business hostage on a platform only we can maintain.
How fast can we start?
Usually within a week or two of the first call, depending on what's in front of us.
Let's find out what's actually broken.
Fill this out and I'll come back with whether a Teardown makes sense for you, or whether you need something else entirely. If it's not a fit, I'll tell you that.