Frequently Asked Questions
Do you work with startups or only established companies?
Both. Startups need a technical foundation that won't need to be rebuilt at their next stage; established businesses need systems that fit how they already operate. We scope differently for each, not the same package for everyone.
Do you use WordPress or a page builder?
Not for custom application work. We build with PHP directly (and Laravel where its structure genuinely helps) so the site or system isn't constrained by a plugin ecosystem. See Technology for specifics.
Can you take over an existing codebase?
Yes — we regularly stabilize and extend existing PHP applications rather than starting from zero, once we've had a chance to audit what's there.
How is pricing structured?
It depends on scope — fixed-price for well-defined projects, or a discovery phase first when requirements need to be scoped out. Share your budget range on the quote form and we'll tell you honestly whether it fits.
Do you offer ongoing support after launch?
Yes — our process includes an Optimize stage rather than treating launch as the end of the relationship.
Where are you located and do you work remotely?
kyenet is based in Lagos, Nigeria. We work with clients across Nigeria and internationally, remotely as standard practice.
Do you work with clients outside Nigeria?
Yes. Being based in Lagos doesn't limit who we work with — we run projects remotely with clients in other countries and time zones as a matter of course.
How long does a typical project take?
It depends entirely on scope — a focused marketing site can take a few weeks; a custom application with integrations can take several months. We give a realistic timeline during the Strategize stage, once we understand the actual requirements, not before.
What happens if I need changes after the project is delivered?
Minor fixes are typically covered for a period after launch under the project agreement. Beyond that, we offer ongoing support and iteration as a separate arrangement — ask us to include this when scoping the project if you know you'll need it.