2 · day rate
by the day
priced after a short call
For ongoing work, joining your team, or when the scope is still moving.
- billed for days worked, nothing else
- a weekly note of days used
- same tests, previews and hand-over
tony@sala.dev:~ $ cd process
~/process $ cat steps
Five steps from the first call to the hand-over. You see working software every week, and you own all of it at the end.
how a project runs
1 · timeline 1/5 open
-
WHAT HAPPENS
- We talk through the problem, who it is for and what done looks like
- Constraints: budget, deadlines, existing systems, compliance
- If I am not the right fit, I say so on the call
YOU RECEIVE
- a short written summary of what I heard
- a clear yes or no on fit, and the next step
$ curl sala.dev/contact -d "call=discovery"
-
WHAT HAPPENS
- The call becomes a written plan: scope, milestones, risks, and what is out of scope
- An estimate as a range in days, or a fixed price for a fixed scope
- You push back; we adjust until it reads right to both of us
YOU RECEIVE
- plan.md — scope, milestones, risks
- an estimate or a fixed quote
$ sala plan --from=call-notes.md > plan.md
-
WHAT HAPPENS
- Each week a working slice lands on a preview URL
- Tests first; CI runs on every push
- A short weekly note: done, next, blocked
YOU RECEIVE
- a live preview link
- access to the repository from day one
- a weekly changelog
$ git log --since="1 week" --oneline
-
WHAT HAPPENS
- The pipeline builds, runs the whole suite, and only then deploys
- Rollback is one command, and it is tried before launch
- Alerts for the things that actually break
YOU RECEIVE
- green CI on main
- a production deploy
- a rollback you have seen work
$ make ship # build → test → deploy $ make rollback # one command back
-
WHAT HAPPENS
- Docs: README, runbook and architecture notes
- Every account moves to you: repos, hosting, domains, keys
- Optional support on a monthly retainer
YOU RECEIVE
- the code, the accounts and the docs
- a walkthrough of the system
- a support option, never a lock-in
$ chown -R you:you ./project
ways to work together
3 · fixed-scope project
one agreed price
fixed after the written plan
For a clear piece of work, priced once the written plan is agreed.
- price fixed after step 2, not before
- changes are scoped and priced openly
- weekly previews all the way through
4 · monthly retainer
hours to suit
agreed month by month
For after launch: keeping it patched, upgraded and moving.
- security and dependency updates
- PHP and framework upgrades
- small features from a shared list
project estimator
[!] rough guide, not a quote
5 · inputs
PROJECT TYPE
SIZE
7 · next