How we work
together.

Hey, before we start

These are the ground rules for working together. Nothing crazy - just a shared understanding of how projects go, what you can expect from me, and what I'd appreciate from you. If something here isn't clear, just ask. I'd rather talk it through than have either of us surprised later.

What I do

I offer freelance technical services: web development (frontend and backend), Linux server setup and administration, networking and infrastructure, Docker and containerization, and related consulting. Every project is scoped individually - we'll agree on exactly what's included before anything starts.

How a project works

• You reach out:Fill out the form, describe what you need. I'll get back to you.
• We align:We talk through the scope, timeline, and price. Nothing starts until we both agree in writing - email counts.
• I build it:I work on the project and keep you in the loop. If something comes up that changes the scope, I'll flag it before doing anything extra.
• You get it:Final deliverables are handed over once everything is wrapped up and payment is settled.

Payment

Pricing is agreed before work begins - no surprises. For bigger projects, I may ask for a deposit (up to 50%) upfront, with the rest due on delivery. If payment terms aren't being met, I reserve the right to pause work until things are sorted.

Prices are quoted in whatever currency we agree on. If taxes apply on your end, those are yours to handle.

Revisions

Reasonable tweaks within the agreed scope are included - I'm not going to nickel-and-dime you for small changes. But if you want to expand what was originally agreed, that's a new conversation. I'll always give you a heads-up before any extra charges.

Who owns what

Once you've paid in full, the final deliverables are yours. I may keep a reference to the work in my portfolio unless you specifically ask me not to. Any open-source libraries or third-party tools used in the project stay under their own licenses.

Anything I built that didn't make it into the final product - drafts, experiments, unused code - stays with me.

Keeping things private

Whatever you share with me about your project stays between us. I won't discuss it with anyone else or use it for anything other than your project. On the flip side, I'd appreciate the same courtesy - please don't share tools, methods, or work-in-progress materials I send you without checking with me first.

If things don't work out

• You cancel:If you need to stop the project after work has started, you'll owe for what's been completed. Any upfront deposit isn't refundable - that covers the time I've already put in.
• I cancel:If you go quiet for more than two weeks, miss agreed payment milestones, or ask for something I'm not comfortable with, I may end the project. In that case, I'll refund you for any work that hasn't been started.

Realistic expectations

I do my best work and stand behind it. That said, if something goes wrong, my responsibility is limited to the amount you paid for the project - I can't be on the hook for things beyond my control or indirect consequences down the line. I'll always do my part to make things right.

One simple rule

Don't ask me to build something harmful, illegal, or deceptive. I get to decide what that means, and I'll always be upfront if a request doesn't sit right with me.

Updates to these terms

If I change anything here, I'll update the date at the top. If you're already mid-project when something changes, the terms you agreed to at the start still apply.

Still have questions?

Totally fair - just email me at contact@ayopili.com. These terms exist to protect both of us, not to create distance. Let's just talk.