Look at relevant work
Look beyond a list of skills. Read the examples and the person’s role in making them.
Work with developers
Find a developer.
Make something happen.
From web apps and sites to integrations and APIs, find someone who understands what you need. Look at their work and start with a conversation.
DevelopmentOne less thing to do by hand.
enquiry.received → check the details → send a warm welcome → make a place in the planner
Small tasks. Bigger projects.
What could you
make together?
Start with the outcome. These are some of the things developers can help bring into the world.
A good start makes
the work better.
Use the conversation to make the details clear before committing.
Talk through your idea
Explain the outcome, timing and constraints. Ask what they need from you and what is included.
Make the scope clear
Agree the deliverables, review stages and price. A short shared brief is a better start than assumptions.
A brief you can both use
Be specific about
what good means.
Example acceptance criteria for developers. Adapt them to your project.
- Checkout completes with a test card on staging; errors are shown inline.
- The existing test suite passes; new code ships with tests.
- Deployed to the staging URL with a short handover note.
Keep the feedback
with the work.
A delivery opens as a diff with a line gutter. A note attaches to the line it is about, and approval is against the acceptance criteria you both agreed — not against a feeling about the demo.
Priced as fixed deliveries — a feature, a release, a fix — or by the hour as described work, never surveilled.
See the full process ↗Know what the evidence means.
Uploaded work is a person’s own claim. A platform provenance badge links to a qualifying delivery; it does not certify every skill or guarantee a future result. Reviews provide another perspective.
Live payments are not enabled yet. Payment screens currently demonstrate the workflow; no real money is collected or protected.