System operational

Structured project intake

Answer nine questions. Get a scoped delivery plan.

The ASKO intake questionnaire walks through your goals, technical direction, scope, budget and timeline. One engineer reads every response and replies with a plan you can act on.

Start the questionnaire
  • 9 guided steps
  • About 12 minutes
  • Draft autosaved
  • Reply in 1 business day

No account needed. Your answers stay in this browser until you submit them.

STEP 04 / 09 Full name Work email Project summary Web application API & backend Draft saved Resume any time About 12 min 9 guided steps
Why we ask

A short form that saves a week of back and forth

Generic contact forms produce vague quotes. These nine steps capture the detail an engineer needs to size the work, sequence the phases and give you a realistic range before anyone signs anything.

  • Scoped on the first reply

    Goals, constraints and non-goals in one place, so the first response already contains a plan instead of more questions.

    • Phases and deliverables named up front
    • Assumptions listed explicitly

  • Technical detail engineers understand

    Stack, integrations and access requirements are collected in the same vocabulary we use internally, which removes a full email thread.

  • Budget clarity earlier

    An honest range protects both sides. We tell you what is realistic for the outcome before any commitment is made.

  • Decision makers identified early

    We capture who signs off and how decisions are made, so proposals reach the right person the first time.

  • Nothing gets lost

    Progress is written to this browser as you type. Close the tab, come back tomorrow, and continue from the same step.

  • Human review, always

    No automated triage, no chatbot. A named engineer reads the answers and responds within one business day.

  • 9 Guided steps
  • 12 Minutes to complete
  • 1 Business day to reply
  • 100 Reviewed by an engineer
Before you start

Have these four things ready

You do not need a finished brief. These four items are enough to complete every step.

  1. A short description of the problem

    Two or three sentences on what is not working today and what better looks like.

  2. Your decision process

    Who approves the work, and whether consensus or a single sign-off is needed.

  3. An honest budget range

    A ballpark is fine. Ranges get refined during scoping, not renegotiated later.

  4. Any links that matter

    Existing repositories, briefs, mockups or a competitor whose behaviour you want to match.

The questionnaire

Nine steps, about twelve minutes

Required fields are marked with an asterisk. Everything is validated as you move between steps, and you can jump back at any time to change an answer.

    Step 1 of 9

    Start here

    First, tell us what brought you to us so your answers reach the right person.

    What brings you here today?

    Choose the option that matches your situation best.

    A referral, a search, or a colleague you already work with.

    Step 2 of 9

    Who is asking?

    We only ask for the details we need to reply to you properly.

    The name we should use in your proposal.

    Use an address we can reply to without chasing you.

    Include the country code if you are outside Ghana.

    Company, agency, school or your own name if you are independent.

    Preferred contact method
    Step 3 of 9

    Project overview

    Describe the problem in your own words. Plain language is fine.

    A short internal name, for example “Member portal rebuild”.

    At least 40 characters. Two or three sentences is plenty.

    The more concrete this is, the more useful our first reply will be.

    Numbers help us propose the smallest solution that actually hits them.

    Step 4 of 9

    Technical direction

    Rough answers are fine. We will confirm the detail together.

    Which services do you need?

    Select everything that applies.

    Include versions where it matters, for example “Node 20, PostgreSQL 16, AWS”.

    Name the systems and whether you already hold API access.

    Will we have repository access?
    Step 5 of 9

    Scope and boundaries

    The most useful section for keeping a project on budget.

    For example: “Deployed web app”, “Admin training session”, “Source code handover”.

    Naming exclusions now is the cheapest way to protect the budget.

    Leave blank if this has not been discussed yet. It affects hosting cost.

    Step 6 of 9

    Budget and commercials

    Ranges, not quotes. We refine these together during scoping.

    Preferred payment model
    Funding status
    Step 7 of 9

    Timeline

    Fixed dates help us plan around your constraints instead of ours.

    Leave blank if you need an estimate from us.

    How urgent is this?
    Step 8 of 9

    People and decisions

    So we know who to talk to and how quickly decisions can happen.

    The person who approves scope, budget and start date.

    Knowing the approval rhythm keeps momentum after kick-off.

    Step 9 of 9

    Review and send

    Check the summary below. Use the edit links to jump back to any step.

    How we handle your answers

    Short version: your answers stay on your device until you send them, and we use them for one purpose only.

    • Draft answers are stored in this browser only, and are never transmitted while you type.
    • Submitted details travel over HTTPS and are visible only to the engineers preparing your proposal.
    • We never sell or share your information with third parties or advertising networks.
    • Ask us to delete your submission at any time and we will confirm within two business days.
    Questions

    Frequently asked questions

    How long does the questionnaire take?

    Most people finish in about 12 minutes. Progress is saved in your browser as you type, so you can stop and continue later on the same device. There is no timeout and no account to create.

    Do I need an account to start?

    No account is required. The questionnaire is a single page with nine steps, and you receive a reference number as soon as you submit so you can quote it in any follow-up message.

    What happens after I submit?

    An engineer reviews your answers and replies within one business day with either scoping questions or a proposed plan, timeline and budget range. Emergency requests are triaged first.

    Is my data stored safely?

    Answers stay in your own browser until you submit. Submitted details are used only to prepare your proposal and are never sold or shared with third parties.

    Read the privacy summary
    Can my company send this link to colleagues?

    Yes. Use the copy link button in the “What to expect” section. Add a step to the URL, for example ?step=budget, to send someone straight to a specific question.

    I am not sure about the budget. What should I choose?

    Choose the closest range and mark the funds as not yet secured. Budget is refined together during scoping, so an early estimate is enough to start.

    Contact

    Prefer to talk to a person?

    Reach us on any channel below during business hours, or send the questionnaire link if you would rather answer in writing first.

    Or send a message first

    Tell us briefly what you need. On submit you will be taken straight to the nine-step questionnaire with these details carried over, so you do not have to type them twice.

    The name we should use when we reply.

    We reply to this address within one business day.

    Include the country code if you are outside Ghana.

    Company, agency, school or your own name.

    This sets the first answer in the questionnaire.

    At least 20 characters. We read every message ourselves.

    Nothing is shared with third parties. You will stay on this page and get a reference to quote in your reply.

    Ready when you are

    Nine questions now saves a week of emails later. Your progress is saved as you type.

    Start the questionnaire

    No account required Draft saved in your browser Private by default