Skip to content
Gus Skarlis
01 · Consulting

Advice from someone who has to live with it.

I build and operate the same class of system I am advising you on. That constrains what I am willing to recommend, which is the entire point. Every engagement is a fixed question with a fixed fee, and it ends in a document you own.

02 · Engagements

Three shapes of work.

Each one is scoped to a question and ends when the question is answered.

Vendor review.

You have quotes from three suppliers and no way to compare them. I read the contracts, test the claims, and tell you which one survives contact with your operation.

  • Written verdict, not a scorecard
  • Claims tested against the actual product
  • Contract and lock-in terms read closely

Build or buy.

The most expensive decision in a software project is made before anyone writes code. I cost both paths honestly, including the one that loses me the build work.

  • Total cost over three years, not month one
  • What breaks if the vendor disappears
  • A recommendation with its reasoning attached

Systems architecture.

For teams that have decided to build. What the pieces are, how they connect, what order to build them in, and which parts are not worth building at all.

  • Component map and data model
  • Sequenced so each stage ships something usable
  • Written to hand to whoever implements it
03 · From a proposal?

The smallest way to start is a single question.

If a proposal brought you here, consulting is the lowest-risk first engagement: one fixed-price milestone, one written deliverable, and you decide what happens next with the answer in hand.

The conversation stays where it started: reply to the proposal with the question you need answered and I will scope it there.

ContractFixed price, one milestone
MilestoneThe written recommendation
ScopeAgreed in the proposal thread first
MessagesOn the marketplace until the contract is signed
RevisionsOne round of questions on the document, included
04 · Rates

Three ways to buy the time.

A single call, a block of hours you can spend on development or consulting, or a standing monthly arrangement. Every one starts with the question written down.

30-Minute Call

$250one call

Bring the question. Leave with an answer.

A working session, not a sales call. One decision, talked through.

  • Thirty minutes, on video or phone
  • Vendor, architecture or build-or-buy question
  • Written summary of the recommendation afterwards
  • Credited toward a block or a month if you continue

Most start here

10 Hours

$2,500block of hours

Development and consulting, on the clock.

Budget in hand, a defined piece of work, no long commitment.

  • Use across development and consulting as needed
  • $250 per hour, paid up front
  • Hours tracked and reported as they are used
  • Scope agreed in writing before the clock starts

Monthly Fractional

$5,000per month

A standing technical lead, without the hire.

Operations with decisions in flight every week and no one to own them.

  • Standing weekly slot plus a direct line
  • Vendor evaluations, architecture and roadmap owned
  • Development hours included as the month needs
  • I brief your team and read what they ship

Month to month

The call is credited toward a block or a month if you continue. Prefer written answers only? Counsel starts at $99 a month at pushbuttonai.com/counsel.

On Upwork or Freelancer these are contracted as fixed-price milestones at the same rates, through the platform.

05 · How it runs

Scoped tight, written down, no retainer.

An engagement is a fixed question with a fixed end. If it turns into ongoing work, that is a separate conversation we both agree to.

QUOTES AND CLAIMSA WRITTEN VERDICT
Fig. 02 — From scattered inputs to an ordered recommendation.
06 · Terms

What you get, in plain terms.

FormatFixed scope, fixed fee
OutputA written recommendation
OwnershipThe document is yours
RetainerNot required
ImplementationOptional, quoted separately
07 · Where it leads

The recommendation is the end of the engagement, not the relationship.

When the answer is build it, the architecture goes straight into a PushButton Build quote. When the answer is keep going, the block and the month are already priced. Either way you are free to take the document elsewhere.

If the answer is build.

The architecture document becomes the brief. PushButton Build quotes it at a fixed price, runs the build in a client portal, and hands over the source at the end.

If the answer is keep going.

The same rates carry on: a ten-hour block for the work that follows the recommendation, or a monthly arrangement when the decisions keep coming.