Each one is a different answer to a different question: does this work at all, can it go into the product we already ship, can this process run without people, and who keeps it running afterwards.
01
02
03
04
USD, always. Model provider and infrastructure costs are billed to your own accounts rather than through us, so there is no margin on your usage.
engineering / pricing
Because the alternative is that an engineering leader with a real project has to sit through a discovery call to find out whether the number starts with a two or a two hundred. Both sibling practices at Thinkscoop publish theirs. Withholding it filters for patience rather than for fit.
The number of external systems that have to be integrated, whether the build has to run inside your own tenancy from day one, how much of the process exists only in people's heads at the start, and the size of the compliance surface. Not how large your company is.
Model provider and infrastructure costs, which you pay directly on your own accounts, so there is no margin on your usage and no incentive for us to be relaxed about your token spend. Third party licences are also yours and named in the scope before signature.
The sprint is fixed fee in instalments against milestones. The integration pod and the workflow build are billed monthly against a fixed capacity, with the workflow build carrying a stopping point at the end of design. The embedded pod is monthly in advance, three month minimum, then rolling with 30 days notice. USD throughout.
Most briefs arrive as one and turn out to be another. Describe the problem and you get a written view of which it is, and whether it is one at all, within a working day.