How we work with you

Three ways to engage, one way of communicating, and the same rules about quality, security and ownership every time. For the stages of a project, see how we deliver software.

Engagement models: fixed scope, dedicated team or product partnership

Fixed scope

Best for
A defined project: a website, a first release of an app, or an integration.
How it works
Discovery produces a written scope with milestones. We deliver milestone by milestone, and each one is demonstrated and signed off.
Billing
A fixed price per milestone. Changes go through a short change request, with their cost and time agreed before we start them.
Worth knowing
It works when the scope is clear. If you expect to learn a lot along the way, a dedicated engagement is the better fit.

Dedicated team

Best for
A product with a backlog that keeps changing.
How it works
We work in your sprints, covering design and QA as the work needs them. You set the priorities for each sprint; we plan the work, build it and test it.
Billing
Monthly, for an agreed amount of time each month, with a notice period instead of a fixed end date.
Worth knowing
You need someone on your side who can decide priorities every two weeks.

The dedicated team in detail

Who's on it
The people your backlog needs: developers, with design and QA brought in when the work calls for them, and one named contact who runs the sprints with you.
How priorities are set
You set them at the start of each two-week sprint. We plan the work, build it and test it, and show it to you in a demo at the end of the sprint.
Hours of overlap
9:00 to 18:00 Pakistan time on weekdays and 10:00 to 16:00 on Saturdays. For clients in the Gulf, see the times in the UAE and Saudi Arabia.
If someone changes
We tell you before it happens and hand over inside our team. The code, the decisions and the open tasks are already written down in your repository and on the task board, so the work carries on.
Notice period
Either side can end the engagement with 14 days' written notice, as set out in our terms of service. You pay for the work done up to that date.

Product partnership

Best for
Founders who want a technical partner to build and run the product with them.
How it works
We plan the roadmap together, then build, host, monitor and support the product, releasing in regular cycles. It's how we run our own product, BrokLeads.
Billing
Agreed case by case. Usually a monthly fee covering development, hosting and support.
Worth knowing
It's a long-term commitment on both sides, so we start with a discovery phase to be sure it fits.

See it in practice: how we build and run BrokLeads.

Which model fits

Fixed price or a dedicated team is mostly a question of how settled the scope is. If you're not sure, start with a short discovery and choose once the scope is written down.

The three engagement models compared
Fixed scopeDedicated teamProduct partnership
Best whenThe scope is clear and the project has an endThe backlog keeps changingYou want a partner to build and run the product
The scopeWritten and signed off before we startPlanned sprint by sprintA roadmap we plan together
You decideSign-off at each milestoneThe priorities for each sprintThe roadmap, with us
BillingA fixed price per milestoneMonthly, for an agreed amount of timeAgreed case by case, usually monthly
ChangesA short change request, costed before we start itGo into the next sprintGo onto the roadmap

Working with clients in the UAE and Saudi Arabia

We work with clients in the Gulf remotely from Lahore. Here is what that means for hours, weekends and the way we run the project.

  • No Gulf office

    We don't have an office in the UAE or Saudi Arabia. The team works from Lahore, and calls, demos and reviews happen online.

  • Time zones

    Pakistan time (UTC+5) is 1 hour ahead of the UAE (UTC+4) and 2 hours ahead of Saudi Arabia (UTC+3). Our weekday hours are 8:00 to 17:00 in Dubai and 7:00 to 16:00 in Riyadh.

  • Weekends

    Our week runs Monday to Saturday, with a shorter Saturday and Sunday off. Most UAE businesses work Monday to Friday, so we share every working day. In Saudi Arabia the weekend is Friday and Saturday, so we overlap Monday to Thursday, and Sunday is your working day and our day off.

  • Calls and paperwork

    Calls, written updates and documents are in English. Every engagement has a written agreement, and the ownership and security rules below are the same wherever you are.

  • Lahore, our team (PKT, UTC+5)

    9:00 to 18:00

    Monday to Friday, and Saturday 10:00 to 16:00

  • UAE (GST, UTC+4)

    8:00 to 17:00 your time

    Shared working days: Monday to Friday

  • Saudi Arabia (AST, UTC+3)

    7:00 to 16:00 your time

    Shared working days: Monday to Thursday

Our weekday hours, shown in local time on each side.

Communication

You have one named contact for the whole project. You get a written update every week and a demo at the end of every sprint, and you never have to chase us for status.

  1. Mon, week 1Sprint plan
  2. Tue, week 1
  3. Wed, week 1
  4. Thu, week 1
  5. Fri, week 1Written update
  6. Mon, week 2
  7. Tue, week 2
  8. Wed, week 2
  9. Thu, week 2
  10. Fri, week 2Written updateDemo
Between those, questions are answered in the shared channel during working hours, and every change is on a preview link as soon as it's pushed.

Tools

Everything lives somewhere you can see it, and the important things live in accounts you own.

Tools we use on a project, what for, and who owns them
ToolWhat forLives in
GitHub (or your GitLab)Code, pull requests and reviewsYour organisation
A task boardThe backlog, sprint plan and every piece of feedbackShared with you
Preview deploymentsA live link for each change, before it reaches productionYour hosting account
Design filesWireframes, prototypes and the design systemShared with you
WhatsApp or SlackQuick questions during working hoursA channel for the project

Quality: what "done" means

A task isn't done when the code is written. It's done when all of these are true.

  • It works on a real phone and a desktop browser
  • It passes typecheck, lint, the automated tests and a production build
  • Every form field has a label, and it can be used with a keyboard
  • Errors say what went wrong and what to do next
  • Every change is reviewed before it's merged
  • It's on the preview link, and you've seen it

Security

  • Secrets stay out of the code

    API keys and passwords live in environment settings, never in the repository, a document or a chat.

  • Least-privilege access

    We get the access the work needs, in your accounts, and it's removed when the engagement ends.

  • Your data, walled off

    For multi-tenant systems, each customer's data is scoped on every request, the way BrokLeads keeps each branch's data separate.

  • Only the data you need

    Forms and databases collect what the job requires and no more, with a privacy policy that says where it goes.

  • The basics, always

    HTTPS, security headers and dependency updates. We set up backups and test a restore before launch.

Intellectual property: who owns the code

The short version: the work we do for you is yours, and it lives in your accounts from the start. The questions clients ask most, answered plainly.

Who owns the code, and when?
You do. Under our terms of service, you own the final deliverables created for your project once all fees are paid. The code lives in your repository from the first commit, so you can see it at every stage.
What does Teknoesis keep?
Only the general frameworks, libraries and tools we developed independently and use across many projects. Open-source libraries in your project keep their own licences.
Whose name are the accounts in?
Yours. Hosting, domains, app store listings and third-party services are created in your organisation's name, and we're given access to them. Nothing important is held by us unless we agree otherwise, for example when we host a product for you.
How does handover work?
The code, the accounts and the documentation are already yours, so a handover is a walkthrough, not a negotiation. We take your team through the system, the deployment and the open work, and our access is removed when the engagement ends.
Is what we share kept confidential?
Yes. Our terms include a confidentiality clause: both sides keep each other's sensitive information confidential, and that continues after the project ends.

This is a plain summary, not legal advice. Our terms of service and the written agreement for your engagement are what apply.

Questions about working together

Do you sign contracts and statements of work?

Yes. Every engagement has a written agreement or statement of work that sets out the deliverables, timeline and payment schedule, alongside our terms of service.

Can we start small?

Yes. A short discovery or a small fixed-scope milestone is a good way to see how we work before committing to more.

What time zone do you work in?

Pakistan time (PKT, UTC+5): 9:00 to 18:00 on weekdays and 10:00 to 16:00 on Saturdays. Calls go in the hours we share with your team; the times for the UAE and Saudi Arabia are set out above.

Do we need to visit you in Lahore?

No. Discovery, demos and reviews all work online, and most of our communication is written down, so nothing depends on being in the same room.

Where to go from here

Tell us what you're building

A few lines is enough. We'll ask the right questions on the call.

  1. We reply within one working day

    By email or WhatsApp, whichever you prefer.

  2. A short call

    To understand the goal, the people who'll use it and any deadline.

  3. A written scope and estimate

    Before any work starts, so you know what you're agreeing to.

Prefer to talk first?

So we can reply on WhatsApp if you prefer.

What are you building, who is it for, and is there a deadline?

We reply within one working day. By sending this you agree that Teknoesis (Lahore, Pakistan) may contact you about your request and store your details as described in our Privacy Policy. We use analytics tools; see Your Privacy Choices in the footer.