Async DevOps Consulting, Not Booked Calls

Async DevOps consulting means pricing infrastructure work — a pipeline review, a Kubernetes config fix, a cloud cost audit — as a fixed-scope request a follower submits with files and pays for upfront, instead of a booked call. The consultant replies with written notes, a fixed file, or a recorded walkthrough on their own schedule. Custom Work lets you offer clearly scoped commissions and services: you set the price, the scope and the delivery time, and followers submit a brief and pay before you start.

No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate. Followers need no account, Custom Work is one-time purchases rather than memberships, and creators in 41 countries can get paid (pricing). A one-time purchase ends when the pipeline review is delivered; unlike a membership, it does not leave you with members, a publishing schedule or a shared conversation to keep running.

DevOps work tends to arrive as a DM after a conference talk: "Can you look at our pipeline?" or "Got 20 minutes to check our K8s setup?" The instinct is to offer a call. But most of those requests aren't asking for a conversation — they're asking for a diagnosis, which can usually be delivered in writing, on the consultant's own time.

Infrastructure complexity is why the unpaid-review backlog keeps growing. Production Kubernetes usage rose to 82% of container users in 2025, up from 66% in 2023 (CNCF, Annual Cloud Native Survey). Among AI adopters, 66% now run Kubernetes to scale inference workloads, per the same CNCF survey (Linux Foundation, "Kubernetes Fuels AI Growth") — a fresh layer of configs written quickly and reviewed rarely.

"Over the past decade, Kubernetes has become the foundation of modern infrastructure. Now, as AI and cloud native converge, we're entering a new chapter." — Jonathan Bryce, Executive Director, Cloud Native Computing Foundation, CNCF Annual Cloud Native Survey announcement

On Brillay, a client chooses an offer, pays upfront, and submits the required file — a workflow config, a docker-compose.yml, or a billing export — through the creator's page (Custom Work).

What does "async DevOps consulting" mean in practice?

Async DevOps consulting in practice means turning one recurring technical request into a priced offer with a defined input, a defined output, and a stated delivery time, answered without a live meeting. The listing reads "send your pipeline config and its failing run logs, get a written breakdown back within 48 hours" instead of "book 30 minutes with me."

An async DevOps offer is not a broad "hire me as your consultant" retainer. It is a scoped deliverable: one pipeline reviewed, one config diagnosed, one cost report annotated — sellable at a fixed price instead of an hourly rate that has to be negotiated first. A creator can list several narrow offers side by side, such as a CI/CD pipeline review — a security-minded counterpart can run the same way, structured as async security consulting instead of a booked audit call — rather than one vague "DevOps consulting" listing nobody knows how to price against.

Why do DevOps consultants avoid booking calls for this work?

DevOps consultants skip booked calls for review work because the value sits in reading the config and writing back findings, not in real-time discussion, so the scheduling step buys neither side anything. A call also forces two people onto one clock, which is an unnecessary cost for a distributed, remote-heavy developer audience.

Remote work is the norm for a large share of that audience: 32.4% of respondents to Stack Overflow's 2025 Developer Survey report working fully remote, against 17.9% fully in person. A calendar invite that assumes a shared time zone excludes a large share of the people most likely to want an infrastructure review; an async request removes the time-zone constraint entirely.

Live calls remain the right format when the value depends on live interaction — walking through a production incident together, or a client who wants to talk through options rather than receive a written verdict. Async DevOps consulting on Brillay uses a submission-and-reply flow, with no live call, no scheduling (how Brillay works).

Which requests fit a quick paid question instead of a full review?

A request fits Paid Questions when it can be answered in writing. Paid Questions let a follower pay upfront to ask one private question, and you send one written reply on your own time — no live call or scheduling.

The rule, stated plainly: use a Paid Question when the client asks in typed text and you answer in writing. Use a custom request when the client needs to attach a file or you need to deliver notes, files, or links. For both, you set the price and delivery time.

Examples that stay in the Paid Question lane: "Is it worth migrating off Heroku this quarter, or is that premature?" and "Which managed Postgres would you pick for a Node API at our scale?" Both are judgment calls rather than diagnostics, because neither needs a log file or a config to answer.

Which requests need a full config or pipeline review?

A request needs a full custom request review whenever the client has to send an actual artifact — a workflow YAML, a Terraform module, a Dockerfile, a billing export — because Custom Work accepts attached files from the client. That review is written for the pipeline that was actually submitted, not recycled from a generic checklist — the creator delivers text plus files of any allowed type and/or a link, sized to what came in.

A Brillay custom request delivery can include a written note plus up to 5 files — video, audio, images, PDF, Word, Excel, or PowerPoint — and a private link (Google Drive, Loom, Dropbox) for anything larger, while the client can attach their own files when they order. For each custom request, you choose a delivery time of up to 5 days.

Cloud-bill reviews are a growing slice of that inbound work. Flexera's 2026 State of the Cloud Report puts estimated wasted cloud spend at 29%, an increase for the first time in five years, driven by surging cloud-based AI workloads.

The delivery time figures in that table are illustrative examples written by this article's authors — they are not Brillay defaults, industry benchmarks, or survey data. Brillay lets you set a delivery time of up to 5 days.

Refunds stay with you as the independent seller: you publish your own refund and correction policy, the client reads it before paying, and you decide each request under that policy and applicable law.

How should you price async DevOps consulting work?

Price async DevOps consulting by scope and delivery time rather than by the hour: the client sees one fixed price for one named result, such as a pipeline review delivered within 48 hours, before sending any files. Tie each price to one accepted input, one delivered output format, and one stated delivery time inside the 5-day cap.

Developers already do a meaningful volume of this work outside a single full-time job: 13.9% of respondents to Stack Overflow's 2025 Developer Survey describe their employment as independent contractor, freelancer, or self-employed — the same population already fielding these DMs unpaid.

DORA's software delivery guide frames the core throughput measure this way:

"Deployment frequency: The number of deployments over a given period or the time between deployments." — Nathen Harvey, DORA, "DORA's software delivery performance metrics"

Deployment frequency is a useful scoping anchor because reviewing a team that deploys daily is a different job from reviewing one that deploys monthly, so a "high-frequency pipeline" review can reasonably be priced above a one-off audit.

A concrete scoped pricing ladder, built on what each tier actually accepts and returns:

• Tier 1 — typed question in, written verdict out. Sold as a Paid Question. Set a Paid Question price that reflects the value of your technical judgment and the time needed to give a useful written answer; you set the price.
• Tier 2 — one file in, findings out. Sold as a custom request: one config or one workflow file plus its logs, returned as written findings, at a delivery time the creator sets within up to 5 days.
• Tier 3 — one file in, corrected artifact out. Priced above Tier 2 because the client receives a fixed config or an annotated billing export in addition to notes, not a diagnosis alone.
• Tier 4 — one file in, recorded walkthrough out. Priced highest of the four, because recording and narrating a review costs time that scales with the size of the submitted artifact.

These four tiers are a scoping structure, not a market rate card. Set each price from the time, expertise, and output involved; you set the price for Custom Work.

What should a DevOps consulting listing exclude?

A DevOps consulting listing should exclude, in writing, everything the price was not set for: live incident response, open-ended retainers, implementation work beyond the review, and whole repositories rather than single files. State the exact input accepted, the exact output returned, and the point at which a larger request becomes a separate paid offer.

Scope should also say whether AI-generated infrastructure code is in bounds, because AI-written configs are now a common source of the files being submitted. The 2025 DORA State of AI-assisted Software Development report found that 90% of technology professionals now use AI at work (DORA, "Moving from AI adoption to effective SDLC use"). Reviewing that output is measurably slower than reviewing hand-written code for many developers: 45% of respondents to Stack Overflow's 2025 Developer Survey named "debugging AI-generated code is more time-consuming" as a top frustration. A listing silent on AI-generated code will still receive AI-generated Terraform and Actions workflows.

Selling a scoped technical review is not the same as offering regulated professional advice, but a creator should still describe their background accurately and avoid implying a certification they do not hold. Custom Work and Paid Questions are available without a consulting credential in Brillay's setup process; local business and professional-services rules still vary by jurisdiction and are not waived by that. Frame the offer around the deliverable, not an implied guarantee about outcomes such as uptime or cost savings.

What else can a DevOps consultant sell alongside this?

One Brillay link can hold your paid config review alongside Tips and Goals, plus a free Brand Collaboration Inquiries form for sponsorships and brand deals. Tips let a supporter send you a one-time amount to say thank you, with nothing to deliver in return; a Goal is one named funding target with a progress bar; and Brand Collaboration Inquiries collects a brand’s budget, timeline, and deliverables into a separate brand inbox.

• Tips: for developers who follow the creator's build-in-public content and want to support it without buying a specific review.
• Goals: cash toward a stated goal with a progress bar — for example, funding time to open-source an internal tool — not a rewards-tier crowdfunding system.
• Brand Collaboration Inquiries: a separate form for dev-tooling vendors who want to discuss a partnership, kept out of the regular request queue.

Compared with a calendar-booking tool built around paid 1:1 sessions, the async Custom Work + Paid Questions combination is the more direct substitute for developers who would rather not sync calendars across time zones — see the developer-focused Topmate comparison for how the two models differ fee-by-fee.

How do you get an async DevOps consulting offer live?

Getting an async DevOps consulting offer live starts with one narrow, file-based service rather than a general "DevOps consulting" listing with no defined input or output. Name the single artifact accepted, the single output format returned, and a delivery time inside Brillay's 5-day maximum, then publish that one offer before adding a second.

Related reading: how to price services without undervaluing your time and getting paid for quick dev questions instead of consulting calls.

Frequently asked questions

Do I need to offer a live call option too?

No — you reply in writing on your own time, with no live call, no scheduling. A creator who also wants to take live calls needs a separate scheduling tool.

Can a client send a whole codebase for review?

Custom Work supports client-attached files, but the offer should state a clear scope — one config file and its logs, not an entire repository.

What's the difference between a Paid Question and a custom request here?

With Custom Work, a client can attach files and you can deliver notes, files, or links. You set the price and delivery time for both, with delivery set for up to 5 days.

What does Brillay charge for this?

The platform fee is set out above and on the pricing page — you don't need a large audience or a follower minimum for it to apply: even a few clients who already ask for pipeline help can use the link. Typical US online-card processing runs about 2.9% + $0.30 per transaction on top, per Stripe's published pricing.

Create your free Brillay page and turn the next "can you check our pipeline?" DM into a scoped, paid review.