Your question is not on this list
Ten answers cannot cover a business nobody has met yet. Ask the real question and a written reply comes back from the person who would do the work — not from a form.
FAQ · maswali
Ask the awkward one.
Ten questions a Kenyan business actually asks before it pays anybody — price, time, ownership, what happens when it breaks at night, and what this studio will not do. The answers below are the same ones you would get on a call.
Ten answers. Open any of them.
The answers
What does it cost, and why is there no price list?
There is no price list because there is no standard job. A one page site for a duka and a booking system that takes payments are not the same work, and a published figure would be wrong for one of you.
What happens instead: we talk, the work is written down as a scope, and you get a quote with a fixed price for that scope before anything is built. You decide with the number in front of you.
If the work changes later, the change is quoted too. No invoice arrives that you have not already seen.
How long does it take?
It depends on the size of the build and on how fast decisions and content come back. The second one is usually the slower of the two.
The timeline is written into the same quote as the price and agreed before work starts. While it runs you get a live link, updated weekly, so you never have to wait for a report to know where it is.
No date is promised on this page that has not first been agreed with you.
Who owns the code?
You do. The code, the domain, the hosting, the database, the accounts, the content — all of it in your name.
Where it is possible the accounts are opened in your name on day one, so ownership is never something that has to be rescued later.
At handover you get the repository, the passwords and a walkthrough. Nothing is kept back as leverage.
What happens after launch?
Handover first: accounts, passwords, code, and a session where you are shown how to change the things you will actually want to change.
After that, care is monthly and optional. Updates, backups, small fixes, keeping the thing current. You can take it, stop it, or never start it.
If you stop paying for care, nothing switches off. The site is yours and it keeps running.
Can I take the project to another developer?
Yes, and it is built so that you can. Standard tools, ordinary code, no in-house framework that only one studio can read.
You already hold the repository and the accounts, so the next developer starts by reading the code instead of begging for access.
If they have a question about how something was built, Ferrin will answer it. Leaving is not treated as an insult.
What if the site breaks at 2am?
The honest version: this is a small studio, not a 24 hour operations desk. No response time and no uptime figure is promised on this page, because promising one you have not agreed to is how people get let down at 2am.
What is true: hosting is chosen so the site stays up without anyone watching it, and the boring failures — slow network, small phone, power cut halfway through a form — are tested before launch rather than discovered after.
If something does break, say so through the contact page or email support@noxeratech.com and it gets picked up. If your business genuinely needs cover through the night, say so at the brief and it is scoped and priced as its own piece of work instead of quietly assumed.
Do you work with people outside Nairobi?
Yes. Kenya is bigger than Nairobi and so is the work. Mombasa, Kisumu, Eldoret, Nakuru, a shop in a town with one mast — same studio, same time zone.
Most of a project happens on a call, on WhatsApp and on a link you can open on your phone. Being in the same room is pleasant, not necessary.
Travel to meet in person outside Nairobi is agreed and costed before it is booked, never added to an invoice afterwards.
How does payment work?
Payment is staged, and every stage is written into the quote you approve before work starts: a deposit to begin, the balance at the points you agreed to.
M-PESA or bank transfer, whichever suits your books. Every payment gets an invoice.
No subscription starts quietly, no card is kept on file, and nothing renews without you saying yes to it.
What does the studio need from me?
One person who can make a decision. Projects stall when every answer has to go round a committee first.
Your content: the words, the photos, the logo if there is one, the price list if you have one. This is what delays projects most often — not the code.
Access to the domain or hosting if it already exists, and honesty about what has gone wrong before. Knowing that early saves everyone weeks.
What will the studio not do?
It will not invent testimonials, reviews, client names, awards or statistics for your site. If you have no reviews yet, the page says so plainly and it still does its job.
It will not copy another company's site, build something designed to mislead the people using it, or take a job where nobody will say out loud what "done" means.
It will not hold your accounts hostage, and it will not pretend to be a bigger company than it is. One studio, in Nairobi, run by the person who writes the code.
Next stop
Get the price for your job, in writing.
A short conversation, a written scope, a fixed quote for that scope. Nothing gets built and nothing gets invoiced before you have said yes to both.