Process clarity
Known rules, exceptions, owners, and acceptance criteria reduce discovery uncertainty.
Pricing
A quote should explain the work before it asks for money.
Processly Labs presents defined projects and one-time support work. The client accepts a written proposal with Alex Vorobyov as the individual seller before Alex issues an invoice for the first milestone.
Price drivers
What changes the size of an automation quote.
A small integration with stable inputs is a different engagement from a multi-system agent handling sensitive documents and material actions.
System access
API quality, authentication, rate limits, vendor review, and source-of-truth decisions shape the build.
Data and risk
Sensitive fields, permissions, retention, residency, and consequence of error add controls and review.
Workflow depth
Branches, documents, model calls, queues, transactions, and reconciliation increase implementation work.
Testing
Representative samples, edge cases, permission tests, evaluation sets, and recovery tests affect effort.
Handoff
Documentation, training, deployment environments, monitoring, and internal ownership define delivery.
Every proposal
The commercial details are part of the deliverable.
- Parties, project boundary, deliverables, exclusions, and assumptions
- Dependencies, client responsibilities, and acceptance method
- Estimated schedule, review windows, and effect of client delay
- Price, currency, taxes, invoice schedule, and payment due dates
- Expected provider, usage, software, and other third-party costs
- Ownership, confidentiality, data handling, and support
- Change, cancellation, refund, liability, and governing terms
Short, separately paid milestones
A proposal may divide payment across discovery, approved design, build, testing, and handoff. Each agreed milestone is invoiced separately and is normally planned for delivery within one to four weeks once its prerequisites are ready. Paying the current stage does not charge the next.
Support is separately scoped and invoiced
A support order states its period or deliverable. Additional support requires a new written approval and a new invoice.
Refund principle
Cancellation before delivery receives a full refund.
Each milestone is a separate, bounded purchase. The client can cancel before work begins or while the agreed deliverable remains in progress and receive a full refund to the original payment method.
A completed milestone is assessed against its written deliverable and acceptance criteria. If Processly Labs cannot materially deliver the promise within the agreed correction period, the client may choose a full refund. Confirmed duplicate charges are also refunded in full.
Read the complete policyPricing questions
Details worth checking before a proposal.
Why are there no public automation packages?
The cost depends on process clarity, system access, data risk, integration depth, testing, documentation, and delivery needs. A public package would either hide exclusions or price a template that may not fit the work.
Do you charge for discovery?
The initial audit request and qualification conversation are free. Detailed workshops, process study, architecture, or a written roadmap may be a paid engagement, with a separate scope and price agreed before payment.
Which currencies do you accept?
Invoices are issued in USD or EUR. The accepted proposal, invoice, and secure Stripe-processed payment page identify the currency and any applicable tax before payment.
Are third-party software costs included?
Only if the proposal says so. Clients usually contract with and pay their cloud, model, workflow, integration, and software providers directly. Expected costs and assumptions are listed before the build.
How are later milestones paid?
Each milestone receives a separate invoice after the related scope is accepted. Paying one invoice does not charge a later milestone. Future work requires a new invoice and an active payment by the client.
Invoices are issued in USD or EUR. The accepted proposal and milestone invoice state the currency, any applicable tax, due date, and payment terms before payment.
Start with the process. Pricing follows the scope.
The audit request gives us enough context to decide whether a useful next step is a short qualification call, paid discovery, a bounded build, or no project.
Request an automation audit