HarleyDoughertyI build small tools for wholesalers so the same order is never typed twice.
See the example ↓“I got my weekends and evenings back. I can breathe again, and that’s immeasurable.”
“It’s freed us up to focus on designing the jewelry we love.”
“We’re a small team, so anything that doesn’t get finished during the day usually ends up on my desk at night. Harley helped simplify some of our recurring paperwork, and I’m spending less time catching up after everyone leaves. It’s been a noticeable improvement in my week.”
“One person on our team knew how to put all our product documents together, which made things difficult whenever she was out. Harley built a straightforward process and walked us through it. Now someone else can step in without having to figure everything out from scratch. That’s been a big help.”
“We had several things we wanted to improve but weren’t sure where to start. Harley helped us choose one task we do every week and gave us a clear price for fixing it. We’ve been using the finished tool regularly, and the difference is easy to see. We’re already discussing the next project.”
What I do
Example 01 · Spreadsheets & documents
A wholesale team copies the same order between files. Here’s one way a custom workflow could connect those steps.
The manual way · Copying
An order arrives in one workbook. Someone puts the same details into another.
| SKU | Color | Units | |
|---|---|---|---|
| 12 | OS-104-OLV-M | Olive | 24 |
| 13 | CT-210-CHK-L | Chalk | 48 |
| 14 | TS-082-INK-M | Ink | 36 |
| SKU | Color | Units | |
|---|---|---|---|
| 8 | OS-104-OLV-M | Olive | 24 |
One order. Two places to maintain.
The manual way · Rebuilding reports
Match the order. Find the packed quantity. Work out what is still left. Repeat next week.
| Order / SKU | Units |
|---|---|
| 1048 · OS-104-OLV-M | 24 |
| 1049 · CT-210-CHK-L | 48 |
| 1050 · TS-082-INK-M | 36 |
| Order / SKU | Packed |
|---|---|
| 1048 · OS-104-OLV-M | 24 |
| 1049 · CT-210-CHK-L | 36 |
| 1050 · TS-082-INK-M | 0 |
| Order | SKU | Ordered | Packed | Left |
|---|---|---|---|---|
| 1048 | OS-104-OLV-M | 24 | 24 | 0 |
| 1049 | CT-210-CHK-L | 48 | 36 | 12 |
| 1050 | TS-082-INK-M | 36 | 0 | 36 |
The useful information is already there.
The manual way · Retyping
Read the paper. Type each detail into Excel. Check it all again before the order moves on.
| Style | Color | Size | Units |
|---|---|---|---|
| OS-104 | Olive | M | 24 |
There’s a better use of your day.
I’ll build a custom workflow around your tools, so your team can get back to the work that needs them.
Let’s simplify your workflow What does it cost you? →A retailer’s order and your product catalog come together. One checked customer order supplies the drafts your team needs.
A customer changes an order. The linked drafts update together, ready for your team to check. Try it yourself below.
You’re the wholesaler. A retailer has ordered 24 olive overshirts. Try changing the quantity to 30.
Olive / M to start · $38 per unit
This is one customer’s order. Stock on hand is tracked separately.
Product subtotal, before tax or shipping.
Review before sending to the buyer.
Check availability before picking.
Requested quantity; no goods marked as packed.
Later, the warehouse records what it has actually packed in Packing Log.xlsx. Match the sales order and SKU to calculate what remains.
18 packed + 0 more = 18 recorded. Order edits never change the packing log.
Download the current customer order as a draft for Excel.
I build and connect the workflow around your tools, documents, and review steps. This example uses fictional data; it shows what a custom connection can do.
Your edits stay on this page and reset on reload. Downloads save to your device. Nothing is sent to a buyer or warehouse.
Example 02 · Incoming orders
Purchase orders arrive as PDFs, emails, and photos. The workflow reads each one, matches products to your catalog, and prepares order lines for a person to check.
Where AI earns its place: reading what people send you.| Item | Qty | Price |
|---|---|---|
| OLV OVERSHIRT MED | 24 | 38.00 |
Deliver by 14 Oct · Boston store
Hi, please put us down for 24 of the olive overshirt in medium at the agreed $38. We need them by 14 Oct.
Fictional order and catalog. Nothing is entered until a person approves it.
Example 03 · Email workflows
Prepare replies from your approved information, in your voice. You decide what can send automatically and what needs a person.
A different task. A workflow built around it.Hi, could you send me your returns policy?
Request within 14 days.
Items must be unused.
Of course. Please request a return within 14 days and keep the items unused.
Let me know if you’d like help with the next step.
Fictional message and policy. This illustration sends no email.
≈ 33 working days a year≈ 260 hours · ≈ $7,800 a year
Request a workflow reviewYour numbers. Not a promise.
I build and implement a custom tool around your workflow. We choose the connections around your tools, bottlenecks, and the way your team works.
It could be an existing workbook, a database, or another tool you use. In our meeting, we agree which information is the source, what should update, and where your team approves the result. Connections and any software costs are scoped before building.
Your workflow shapes the build. We agree on the tools, connections, review steps, and price before development.
Show me your tools, bottlenecks, and the task your team keeps repeating.
Review the scope, price, and team input needed.
I build it, connect the agreed tools, test real examples, and show your team how to use it.
The review is free. Implementation is paid and quoted after we understand the workflow.
I'm Harley Dougherty. I've worked in fashion wholesale and I build software. You work with me from the first conversation through delivery.
Independent builder · MassachusettsYes. The service is built around small wholesale teams with a recurring task that takes more time than it should. The useful starting point is the process itself: how often it happens, who handles it, and what would improve if it became easier.
You do not need a technical brief. Bring one task your team repeats, and we can talk through the steps, the tools involved, and whether it is worth a closer look.
I start by looking at the tools you already use and what they can already do. Where practical, the improvement fits around them. Any required changes are explained before you agree to the project.
I will need someone who knows the process to explain the steps and share representative examples. Your proposal will also set out the input and review time needed from your team during the project.
We agree on the outputs and checks before building. The workflow is tested with representative examples, with review steps for decisions or information that need a person's judgment. Handling exceptions is part of the scope.
Implementation is quoted after we review the workflow. Your proposal explains the project price, any ongoing software charges, handover, included support, and options for further help. You can assess the full arrangement before work begins.
No. Some tasks are better handled with straightforward rules or a small software tool. I recommend the approach that fits the process and explain how it will work.
Yes, this approach can suit other businesses too. Wholesale is the example here; your process determines the tool. We review your files, systems, and available access to agree on a practical integration.
A free 20-minute workflow review
Bring one recurring task. A description is enough to start.
Online review requests are not open yet.
Please leave out customer records and confidential documents.
Privacy information