Process
How a project runs.
From first inquiry to final delivery, every engagement follows the same sequence — so you know what happens next and what is expected from each side.
Twelve steps
Inquiry to delivery.
Each stage has a defined output, so there is always something concrete to review before moving on.
-
01
Project inquiry
You describe what you need through the inquiry form, by email or by phone. If you arrived from a package, the service and package are carried into the form. There is no charge and no obligation at this stage.
-
02
Requirements review
We read what you have sent and come back with questions where the scope is unclear. If the project is not a good fit, we say so at this point rather than later.
-
03
Package or scope confirmation
We confirm whether the published package you selected covers what you need. If it does not, we scope the actual work instead of stretching a package to fit.
-
04
Written proposal
You receive the deliverables, technical approach, assumptions, exclusions, timeline, fee and payment schedule in writing. Nothing on the website is a quotation — the proposal is.
-
05
Agreement or SOW
If you accept, the terms are confirmed in a project agreement or statement of work signed by both parties. That document governs the engagement.
-
06
Stripe invoice
Fahymas LLC issues an invoice through Stripe Invoicing. You receive it by email and pay online using the methods Stripe makes available for that invoice.
-
07
Development
Work proceeds against the agreed scope once the first invoice has cleared. You nominate one person who can make decisions, and receive progress updates through the agreed channel.
-
08
Milestone review
Where the agreement defines milestones, each is reviewed and invoiced as it is reached.
-
09
Testing
Functionality, integrations and responsiveness are tested before handover. Defects within the agreed scope are corrected as part of the engagement.
-
10
Digital delivery
Source code, repository access, deployment to your approved hosting and documentation are handed over. Credentials are transferred through a secure channel. Nothing is shipped.
-
11
Final payment
The closing invoice is issued as set out in the agreement.
-
12
Optional support
Maintenance and further development are arranged separately under their own agreement.
Delivery times published with a package apply to that package scope and start once the brief and any required access are supplied and the first invoice has cleared.
What we need from you
- A description of the objective and who will use the result
- Any existing requirements, designs, documentation or code
- The systems and APIs the project must work with
- Written confirmation that you are authorized to have work performed on those systems, where the project involves them
- Access to accounts, hosting or repositories the project depends on
- One named person who can make decisions during the project
How scope is determined
Scope is written from your stated requirements after the review stage. It sets out what will be built, what is excluded, the technical approach and the assumptions the estimate depends on. Changes after that point are handled as change orders rather than absorbed silently or billed without agreement.
Commercial terms
Fees and invoicing: Payment Policy. Cancellation and refunds: Project Cancellation & Refund Policy. Delivery: Service Delivery Policy.
Last updated: August 11, 2026
Next step
Start at the inquiry.
The project inquiry form collects what we need for the first stage.