What do you need?
A website and a system are priced very differently, so the questions split here.
A website For a business, school, church or NGO - from a company site to an online shop. A system, an ERP or a check on software Software your staff or customers run on, automation and AI, an ERP, or a review of what you have.
What are you trying to fix?
Pick the closest one. If it is two of these, start with the one that hurts more.
A system your staff run the business on Customers, orders, stock, approvals and the reports you decide from. A portal or platform your customers log into Self-service accounts, bookings, statements and paying online. Automation and AI for work done by hand Reading documents, chasing, matching and replying - without anyone doing it. Connecting the systems you already run Payments, bank, accounting and your own systems agreeing with each other. One system for the books, the stock and the payroll Accounts, stock, sales, purchasing, payroll and eTIMS on an ERP. A check on software you already have Built with AI, inherited, or no longer trusted - before it holds real money.
What should it handle? Pick everything you need. Leave out what you could live without for the first version.
Pick as many as apply
Customers, accounts and their history Quotes, orders and invoices Stock across one or more stores Jobs, bookings or work in the field Approvals and who is allowed to do what Documents, contracts and files Reports and dashboards for management
What should customers be able to do? Pick everything you need. Leave out what you could live without for the first version.
Pick as many as apply
Manage their own account and details Pay online by mobile money, card or bank Book, order or request a service See statements, invoices and documents Get updates by email, SMS or WhatsApp Several organisations, each seeing only their own data Use it as an app on their phone
What should run on its own? Pick everything you need. Leave out what you could live without for the first version.
Pick as many as apply
Reading invoices, receipts and IDs so nobody retypes them Sorting incoming messages and drafting replies Matching payments to the right invoice Reminders and follow-ups that send themselves An assistant that answers from your own records Reports compiled and sent on a schedule
What should the connection do? Pick everything you need. Leave out what you could live without for the first version.
Pick as many as apply
Keep records in step between two systems Reconcile the month end without anyone matching rows One set of reports across all of them Warn someone when the numbers stop agreeing
Anything else on it? eTIMS and moving your records across are already in the price.
Pick as many as apply
Kenyan payroll
Anything else on it? With nothing picked, we start with a written assessment.
Pick as many as apply
Kenyan payroll KRA eTIMS on the ERP we already run A written assessment of what we have
What kind of website is it? A business or company website A school, church, NGO or association A personal brand or portfolio An online shop
Do you have a website today? We do not have one yet Replacing a site we already have, with the content moved across
How many pages, roughly? Home, about, services, contact and so on. A guess is fine.
Up to 5 pages 6 - 10 pages 11 - 20 pages More than 20 pages
What should it do beyond showing who you are? A contact form and a WhatsApp button come with every site. Skip this if that is enough.
Pick as many as apply
News or a blog you post to yourself A photo gallery or portfolio Bookings or appointments Payments or donations online A members-only area with a log-in More than one language
Anything you need from us besides the site? Domain, hosting, email and your Google Business profile already come with the site. Skip this if you have the words and a logo.
Pick as many as apply
We write the words A logo and brand colours Search set-up so the pages show up on Google
What does it need to talk to? Each connection is real work: checking it, handling it when it fails, and keeping the numbers agreeing. Skip this if it stands alone.
Pick as many as apply
Mobile money and card payments Your bank An accounting package KRA eTIMS WhatsApp or SMS A system you already run Google or Microsoft sign-in
Where are you starting from? Spreadsheets, paper or nothing yet Replacing a system, with the records moved across Adding to a system somebody else built
How many people will use it? Staff and customers both count.
Up to 10 people 10 - 50 people 50 - 200 people More than 200 people
Who looks after it once it is live? Twelve months of Care is written into every build. Pick the level you would want.
Watched, patched and backed up All of that, plus changes every month
Where are you now? Moving onto an ERP from spreadsheets or an accounting package Already running ERPNext and need it fixed or extended
What does the business look like? One company, one location Several branches, stores or companies We make what we sell
Where did the software come from? We built it with an AI tool We inherited it from another developer It has run for a while and we stopped trusting it
What do you need from us? A go or no-go before we launch The full review, a fix plan and a re-test
When do you need it? Just working out what it would cost In the next three months As soon as possible
On its way
A copy is in your inbox, and we will reply within one working day with what we would do next.
Want someone to check it?
Send it to us and a person who would do the work reads it, tells you what they would change, and replies
within a working day. You get a copy by email.