Choose client projects that fit a hosted API integration

Use qualification to decide the next conversation

Qualification happens before detailed discovery. You need enough information to identify a plausible fit, not a complete specification. Ask what the user must accomplish, which information changes, who may change it and who will operate the result. A short call can reveal whether you are discussing a personal-preference website or a shared operational system.

Set a limit on this early effort and tell the prospect what the next step produces. For example, a qualification note may identify a suitable path and two unanswered questions. Detailed discovery can then be a defined paid engagement when the project needs it. This avoids weeks of free solution design and gives the client a clear reason for any investigation fee.

Start with the capability, not the industry label

A training company and a retailer can both need a simple personal settings area. Two training companies can also need entirely different systems: one saves a learner’s preferences, while another needs instructors to approve results across a shared roster. Industry alone is a weak qualification shortcut.

Gammal Tech provides hosted login and per-user application storage alongside other documented services. The storage contract describes a user-specific JSON object, not a general shared database or ready-made administrator-role system. Describe each requested capability in plain language and match it separately. Retain a trusted existing business system where the operation requires authority or shared state outside the suitable hosted functions.

Score five questions and keep the reason beside each

For this original screening rubric, use 0 for a documented fit, 1 for a bounded question and 2 for a substantial mismatch or unresolved responsibility. The numbers organize your judgment; they are not a security rating or vendor ranking.

A total of 0 to 2 suggests proceeding to bounded discovery, 3 to 5 suggests a specific feasibility step, and 6 to 10 suggests redesign or decline. A critical unresolved permission requirement overrides the total.

Compare two fictional Egyptian enquiries

A Cairo consultancy wants members to save language and lesson position on a public learning site. Its existing process handles course eligibility. You score workflow 0, authority 0, setup 1 because verification is pending, support 1 because the owner has not named a contact, and contracting 0. The total is 2. Proceed to discovery with the two responsibilities written down; do not call the project launch-ready.

An Alexandria distributor asks for several employees to edit stock and approve dispatch from one shared record. It also expects immediate support at any hour without a defined service budget. A simple personal-data integration is not the complete solution. Offer a scoped architecture assessment or recommend an appropriate operational system. Gammal Tech may still serve a suitable supporting function, but the quotation must reflect the whole workflow.

Turn an unknown into a small paid feasibility task

A useful feasibility task answers one decision. Write the question, evidence needed, effort limit and the possible outcomes. For example: “Can the proposed member journey work without a central staff roster?” Interview the owner, map the authority source and produce a short recommendation. Do not promise that an experiment will force an unsuitable product into the role.

Use fictional records in demonstrations and keep account administration client-controlled. Do not request a client’s password, PIN or one-time code to speed up qualification. If setup is incomplete, explain which proof can be collected now and which requires the owner to act. The resulting evidence should make the next quote more reliable, even if the answer is to change direction.

Give a useful answer when you decline

A professional decline identifies the mismatch and an alternative next step. “The requested stock approval requires a shared authoritative workflow; our proposed personal-data pattern does not provide that” is actionable. “Your project is too complicated” is not. Where possible, separate the useful parts you can deliver from the part needing another system or specialist.

Do not turn every uncertainty into an objection. A missing copy deck or a pending owner meeting may be easy to resolve. Focus on factors that change feasibility, delivery effort or ongoing responsibility. The client should leave the conversation understanding why the proposed technology choice fits their actual work, rather than feeling screened against an unexplained internal checklist.

Save a qualification note that discovery can trust

Your deliverable is one page: desired outcome, capability fit, five scores with reasons, critical assumptions, account owner, support expectation and the agreed next decision. Add an expiry trigger such as a new payment flow, a staff approval screen or a change in data sensitivity. Those changes can invalidate the original fit.

Review the note with the prospect before moving into detailed specification. For accepted projects, carry its open questions into discovery rather than asking the same questions again. For declined work, retain the architectural reason without storing unnecessary personal information. Good qualification increases useful conversations and reduces proposals that neither party can responsibly accept.

Common questions

Does a high qualification score mean Gammal Tech cannot help at all?

No. It means the proposed integration needs investigation or a different architecture. A suitable hosted function may still fit alongside a separate trusted operational system.

Should qualification replace paid discovery?

No. Qualification chooses the next step. Discovery defines the requirements, data flow, acceptance and responsibilities in enough detail to support implementation.