Define the work first
A useful price needs a clear scope. A prototype to test an idea and a system connected to company infrastructure are different jobs. Before a proposal, understand the current process, the desired result, the available data, and the systems that need to connect.
What a proposal should include
Scope, deliverables, acceptance criteria and cost. Know what the build includes, what will be tested, and how the handover will work. External costs, such as cloud services, model usage and licenses, are identified separately.
How we price work
A proposal for the work we agree on. aiguys offers scoped projects and ongoing support. The partnership currently publishes no numeric hourly tariff, and build hours are not promised before the problem and data are understood.
Personal prices in older Lee Laster articles describe his practice at the time of publication. They are not aiguys tariffs. To receive a proposal, describe the problem and the result you need.