Featherply

CUSTOM WORKFLOW AUTOMATION

Workflow automation for recurring business processes.

I build custom workflow automation for recurring operational work. Routine steps can run automatically across your rules and systems, while exceptions stay visible and important decisions remain with your team.

Walk me through the process See my automation work

Start with a free fit review.

You’ll speak directly with Brad Conklin.

If I can’t give you a fixed quote yet, the first paid phase is capped at $500 USD.

Pricing and process →

My work includes Full Stack Storage, the SaaS platform I own and built, and Breeze, built for Lightning Transportation while I was at OTR Web Solutions.

Purchase request

PR-1042 · Oct 14, 2024 · Facilities

In progress
  1. Purchase request submittedFrom Ops team
  2. Check business rulesPolicy, vendor, budget + current state

Routine work

  1. Run automated stepsCreate PO, notify vendor,
    update systems
  2. Mark completeResult checked · record updated

Needs review

  1. Send to team reviewOps team
  2. Decision recordedApproved

Sound familiar?

The process is recorded. The next step is still manual.

Dates, records, and statuses may already exist. The manual work is still noticing what should happen next, preparing it, and checking whether it finished.

  • Someone notices the date and starts the next step.

    Billing, notices, and scheduled changes still depend on someone checking the calendar and taking action.

  • Someone prepares the same paperwork again.

    Familiar records are pulled together into agreements, documents, and account updates — by hand.

  • Someone checks whether it actually finished.

    Payments, signatures, and other statuses still need a person to confirm the result and follow up if needed.

Selected work

Recurring work, with the rules and follow-up built in.

Full Stack Storage

Founder and product engineer. Full Stack Storage is the SaaS platform I own and built.

In Full Stack Storage, I built a scheduled rate-change workflow that previews each account against the operator’s rules, explains exclusions, and carries scheduled changes through notices and later account updates.

Full Stack Storage is currently in controlled release. These examples are implemented product workflows.

Choose the rules. Preview the change. Schedule the work.

Set the rules

01 · Operator sets the policy

Target rate
$100
Maximum increase
10%
Minimum change
$2
Review eligibility

02 · System applies the rules

Eligible — continues
  1. ScheduleThe operator commits the plan and timing.
  2. Send noticesThe workflow sends notices when scheduled.
  3. Apply when dueThe new rate takes effect on the scheduled date.
Excluded — stops here
No change scheduled.

Account remains unchanged.

Illustration of Full Stack Storage’s scheduled rate-change workflow using synthetic accounts and test values.

Other implemented workflows in Full Stack Storage

Recurring billing and follow-up

Recurring billing generates invoices, attempts authorized payments, and schedules follow-up after explicit failures. Reconciliation also checks for missing invoices and unresolved payment results, so unfinished work can be identified.

Agreements and completed documents

The workflow prepares agreements, tracks customer signing milestones, and stores completed documents. Recovery checks look for completed signatures whose documents have not been stored successfully, keeping document follow-up connected to the process.

Explore the Full Stack Storage project

Breeze

I designed and developed Breeze for Lightning Transportation while employed by OTR Web Solutions.

A staff decision carries into the operation.

I built Breeze around recurring transportation data and the staff and customers acting on it. Incoming records are normalized and updated; authorized actions carry safely into the operation.

  1. User action

    Load
    FB-104
    Customer
    Cedar Works
    Priority
    Mark as priority

    Authorized user

  2. State checked

    Change permitted

    Current state validated

  3. Record updated

    Load
    FB-104
    Customer
    Cedar Works
    Priority
    Priority set

    Change and actor recorded

  4. Notification

    Email triggered

    To the business contact

Illustration of the Breeze workflow using sample information.

Read the Breeze project account

Build around the rules your team can explain.

Define the trigger and result.

Agree on what starts the process and what counts as complete.

Keep decisions with the right person.

Identify where someone needs to review, approve, or intervene.

Make unfinished work visible.

Decide how exceptions are shown and who handles them.

How projects start

Start with one process your team repeats.

We choose one recurring process with a clear beginning and result. One useful workflow can be the finished project. Further work is optional and approved one phase at a time.

Start with a free fit review.

If the requirements are clear enough, I provide a fixed quote directly. If important questions need investigation first, I’ll propose a small planning phase for one reasonably bounded recurring business process, at an agreed price of no more than $500 USDPrices are shown in USD for a consistent North American reference. Canadian projects are quoted and invoiced in CAD at the equivalent amount. US projects are quoted and invoiced in USD. Once quoted, the project or phase amount is fixed in the agreed currency.. We agree on its scope and price, and you explicitly approve it before work starts.

You do not have to commit to a large build while important questions are still unresolved.

What to share for the free review

Share what starts the process, how often it happens, the people and systems involved, and where someone still has to intervene. A short description or anonymized example is enough.

What you leave with

  • Requirements and findings: how the work happens today, the business rules that matter, and what the review establishes.
  • A recommended approach: what to preserve or change, alternatives, the first useful scope and its boundaries.
  • A basis for implementation: acceptance criteria, dependencies, and a fixed proposal with delivery timing and operating responsibilities when the build is viable and sufficiently defined.

If the right answer is not to proceed, you receive the reasons and alternatives instead. If essential information remains unavailable, the handoff explains what is blocked and what would need to be resolved.

The handoff is yours to keep. You can use it with Featherply, another developer, or nobody.

  1. 01Free fit reviewQuote directly when clearInvestigate important questions only if needed, within an agreed planning cap.
  2. 02You approve the buildFirst useful phaseScope, acceptance criteria, price and timing agreed before implementation
  3. 03Continue if neededAdditional workSeparately agreed and approved, one phase at a time
The fit review and direct quote are free. Planning is optional. You approve each paid phase separately.

Planning follows the process from its trigger through decisions, handoffs, and exceptions. The handoff identifies what can run automatically, what stays with your team, who handles a failed or blocked step, and how the result will be checked. Those rules can improve the process even if you decide not to automate it.

Work directly with Brad Conklin, the developer. Before implementation, we agree on scope, acceptance criteria, price, timing, ownership, handover, ongoing costs, and who supports the workflow after launch.

Walk me through the process

Before you begin.

Do I have to pay to get a quote?

The enquiry and fit review are free. If the requirements are clear enough, I provide a fixed quote directly. If important questions need investigation, I explain the work first and propose a small planning phase with an agreed price of no more than $500 USD. No paid work starts until its scope and price are agreed and you explicitly approve it.

What will I receive from the planning phase?

Planning follows the process from its trigger through decisions, handoffs, and exceptions. The handoff identifies what can run automatically, what stays with your team, who handles a failed or blocked step, and how the result will be checked. Those rules can improve the process even if you decide not to automate it. You keep the documented requirements, findings, recommended approach, scope boundaries, and acceptance criteria. When the build is viable and sufficiently defined, the handoff includes a fixed proposal for the first implementation, with timing and operating responsibilities. If the right answer is not to proceed, you receive the reasons and alternatives instead. You can use the handoff with Featherply, another developer, or nobody.

Can I stop after planning?

Yes. The requirements, findings, and recommended approach remain yours. You can use the handoff with Featherply, another developer, or nobody. Each later paid phase requires separate approval.

Can we keep our existing software?

Often, yes. I first review its built-in automation and supported connections. APIs, exports, imports, or agreed database access may help. The available connection must support the actions the workflow needs to perform.

Can people still review or stop the work?

We define which decisions stay with people and what controls the workflow needs. Depending on the process, that may include a preview, an approval step, cancellation, or a queue for cases needing attention.

What happens if a step fails or does not finish?

We agree on how missing information, unavailable systems, and uncertain results should be handled. That may involve a safe retry, checking the original result, or pausing for a person. We also define who sees and handles unresolved work.

What will a build cost?

The first build is scoped and quoted before implementation. Its cost depends on the process, available system access, business rules, required screens, and exception handling. You approve the scope and price before implementation begins.

Who owns the work, and what costs continue?

You keep the agreed completed deliverables. Ownership of custom code, access, and handover are set out in the scope; third-party software remains under its own licences. Hosting, subscriptions, API usage, and support may carry ongoing costs, which we identify before implementation.

Start a conversation

Which process does your team keep repeating?

Tell me what starts the process, what your team does today, and where work gets held up. A few sentences are enough; you don’t need a technical specification.

I’ll review your message and reply within two business days with any initial questions and a suggested next step. This initial fit review is free.

No paid work starts until its scope and price are agreed and you explicitly approve it.

Privacy and your enquiry

I treat what you share as private and use it only to review your enquiry unless we agree to use it for a project. Share only what you are comfortable sending; a short description or anonymized example is enough to start.

This page may use MaxMind to estimate your country or province from your IP address and adjust its wording. We don’t request precise device location or attach the inferred location to your enquiry. Campaign links can select regional wording independently of your location.

Include how often it happens, the people and systems involved, and a common exception if you know one.

No payment or commitment. This sends an enquiry only. No paid work starts until its scope and price are agreed and you explicitly approve it.

Your message will be delivered directly to Featherply. This form is protected by Cloudflare Turnstile.