How to work with TicTek

Three engagement models, one method. Pick the one that fits your organization; we can switch along the way.

Fixed-scope project

You have a clear need but no in-house tech team. We define the scope together, then build the application against an estimate and a schedule agreed before work starts.

  • Scope, deliverables and milestones agreed in writing
  • Regular demos during development
  • Acceptance testing with you before release

Best for: SMEs and organizations without an in-house development team.

White-label development

You run an agency. You keep the client relationship; we handle all or part of the technical delivery, discreetly.

  • No direct contact with your client without your consent
  • We work in your tools and follow your conventions
  • A single technical contact for your team

Best for: Web, digital and marketing agencies.

Team augmentation

Your team needs extra capacity or a specific skill. One or more TicTek developers work alongside you, inside your organization.

  • Onboarding into your tools: Git, tickets, chat
  • Participation in code reviews and team rituals
  • Volume and duration adjusted to your needs

Best for: Startups, software vendors and in-house tech teams.

Project steps

Every step applies to a fixed-scope project. For white-label or team augmentation, we follow your own process.

  1. Intro call

    A call to understand your need, your constraints and your priorities. No commitment.

  2. Scoping

    Features, users, integrations, risks: we clarify the scope and send you a written summary.

  3. Estimate

    A detailed proposal: milestones, schedule and budget.

  4. Development

    Short iterations and regular demos on a staging environment.

  5. Testing

    Automated tests and acceptance testing with you before every release.

  6. Delivery

    Production release, technical documentation and handover.

  7. Maintenance

    If you wish, we then take care of monitoring, fixes and improvements.

What helps us estimate your project

  • The problem to solve and who will use the software
  • Existing tools or systems to connect
  • Your timing constraints and, if possible, a budget range
  • Any existing material: specifications, mockups, screenshots

Frequently asked questions

How much does a project cost?

It depends on scope, integrations and the expected level of quality. We don’t publish a price list: every project gets a detailed estimate after scoping. Sharing a budget range in the form helps us suggest a suitable approach.

How does remote work happen in practice?

Video calls for key discussions, chat for day-to-day questions, a ticketing tool to track requests, and regular demos on a staging environment.

Do you work with clients in other time zones?

Yes, we work internationally. Madagascar is on UTC+3 with no daylight saving time: one to two hours from France and Switzerland, seven to eight hours from Eastern Canada. At kickoff we agree on regular meeting slots that fit your hours; the rest of the follow-up happens asynchronously in your tools.

Can you take over an existing application?

Yes. We start by reviewing the code, dependencies and infrastructure to assess the project, then propose a takeover plan.

A project, an idea, an application to take over?

Tell us where you stand. We will tell you what we can do, how, and on what terms.

Let's talk about your project