TIK

Deep services instead of shallow offerings.

Four areas form the core of our work. In each one we pick the projects where we can make a real difference, not just deliver and sign off.

Technical advisory

An architecture review and a roadmap built on understanding your business — no canned templates. The output is a document any team can execute.

Who is it for?

Companies running a digital product who need a second opinion, or founders with a new idea who haven't picked a tech team yet.

What problem does it solve?

The architecture grew without documentation, the team is stuck on recurring problems, or founders don't know whether the current stack is worth keeping. Advisory turns this into a documented set of justified decisions.

What's included?

  • Assessment of the current architecture and its risk points
  • A technical roadmap with clear priorities and a time estimate
  • Stack and partner selection (cloud, payments, shipping, etc.)
  • A handover-ready document any execution team can use
  • Optional internal-team training on the chosen stack

How we work

  1. 01

    Discovery call

    A free 30-minute call to understand the current state and the goal. Output: a clear decision on whether the paid engagement is the right next step.

  2. 02

    Discovery Sprint

    One to two weeks of intense work — code review, team interviews, risk analysis.

  3. 03

    Document handoff

    An architectural report covering the current state, recommendations, the roadmap, and a time and cost estimate. The document is yours even if you don't continue execution with us.

  4. 04

    Follow-up (optional)

    Monthly sessions to track recommendation execution with your team or with a different execution team you've chosen.

Technologies we use in this area

Architecture reviewCost analysisTeam interviewsRisk modeling

Frequently asked

The free call lasts 30 minutes; its goal is to understand your need and agree on the next step. The Discovery Sprint is 5-10 days of intensive work that produces an architecture document and a detailed estimate, starting at SAR 7,500.

Yes — we sign an NDA before any disclosure of project details or code.

Yes. We conduct the review directly with the owner without coordinating with the executing team, and deliver a written report you can use as a basis for your decision.

No. The estimate comes as ranges with explicit assumptions. Commitment happens when a separate execution contract is signed.

Systems development

Complex web platforms with deep integrations: CRM, ERP, multi-role internal operations systems. We build for the next 5 years, not the first demo.

Who is it for?

Companies and government entities that need a custom system that off-the-shelf SaaS cannot deliver — complex permissions, approval cycles, custom reporting, and integrations with existing systems.

What problem does it solve?

Operations are run between Excel, WhatsApp, and paper. Data is fragmented and reports take days. A unified system turns this chaos into measurable operations.

What's included?

  • Multi-tenant systems where required
  • Customisable dashboards and reports
  • Granular permissions, roles, and approval authorities
  • Integration with existing systems (accounting, CRM, ERP)
  • A staging environment open to the client throughout development
  • Code in your repository from day one; servers under your name

How we work

  1. 01

    Discovery + architecture

    Two weeks: stakeholder interviews, data-model sketching, user-role definition, flow design.

  2. 02

    Weekly development

    Weekly sprints with clear deliverables. Every week a new staging build for you to test before moving to the next phase.

  3. 03

    Code review

    Every pull request is reviewed by another engineer. Automated tests run before merge. No code lands on main without review.

  4. 04

    Launch + handover

    Production deploy, training your team on system administration, handover of operations docs.

  5. 05

    Maintenance (optional)

    A monthly retainer covering bug fixes, security updates, and new feature work as the need arises.

Technologies we use in this area

LaravelVue / Inertia.jsPostgreSQL / MySQLRedisAWS / DigitalOcean

Frequently asked

Between 4 and 8 months for mid-sized systems (50-150 users, 5-10 roles). Larger systems may need 9-12 months, broken into staged-launch phases.

Yes — code in your repository (GitHub/GitLab) from day one, servers under your name in your cloud account, documentation on your domain. No technical lock-in after delivery.

Yes. We have integration experience with Saudi government APIs (vehicle checks, GOSI employee records, agencies and deeds, commercial registries, the National Address) and we comply with Digital Government Authority requirements and data-protection policies.

Scope is reviewed every week. Small changes inside the sprint we handle directly. Larger changes are documented as a change request with their time and cost impact before execution.

Mobile apps

iOS and Android — Native or Flutter as the case requires. From design to store launch to post-launch performance monitoring.

Who is it for?

Companies serving customers or staff via mobile — consumer apps, internal field-operations apps, or extensions of an existing web system.

What problem does it solve?

The app runs slowly, store reviews are negative, or there is a UX gap between iOS and Android. A properly built app turns mobile into a trustworthy channel rather than a complaint source.

What's included?

  • Arabic-first UX design with testing on real users
  • iOS and Android from a single codebase (Flutter), or native where required
  • Push notifications and integrated payments
  • Crashlytics + analytics from day one
  • Store publishing under your company account
  • Versioning and gradual rollouts

How we work

  1. 01

    UX/UI design

    Interactive Figma designs, tested with 5-7 real users before writing a single line of code.

  2. 02

    Build + test

    Built on a weekly iteration cadence. Internal distribution via TestFlight / Firebase App Distribution for continuous testing.

  3. 03

    Store review

    Metadata, screenshots, privacy policy. Submitting the app to both stores and resolving any review feedback.

  4. 04

    Phased launch

    Released to 10% first, monitored for crashes and reviews for a week, then expanded gradually.

Technologies we use in this area

FlutterSwift (iOS)Kotlin (Android)FirebaseCrashlytics

Frequently asked

Flutter for most cases — single codebase, simpler maintenance, performance sufficient for 90% of business apps. Native (Swift/Kotlin) where deep system integrations are needed (NFC, AR, complex widgets) or for performance-sensitive apps.

Under your name — Apple Developer and Google Play accounts in your name. We just run the process up to launch.

An MVP with core features (sign-in, home screen, 2-3 flows) typically takes 8-12 weeks from start to stores, including Apple/Google review time.

iOS and Android ship annual versions that need testing and adjustments. We offer a monthly retainer covering SDK updates, crash fixes, and small features.

Integrations & APIs

Connecting your existing systems with third-party providers — payments, shipping, accounting, WhatsApp, and CRM/ERP platforms.

Who is it for?

Companies with a working system that operates in isolation, looking to integrate with a payment provider, shipping carrier, accounting system, or a communication channel like WhatsApp Business.

What problem does it solve?

Staff re-key the same data into 3 systems, human errors accumulate, and reports are inaccurate. Automated integration eliminates the manual step and produces unified data.

What's included?

  • Local payment gateways: Mada, HyperPay, PayTabs, Moyasar, Tap
  • Shipping carriers: SMSA, Aramex, Naqel
  • Accounting systems: QuickBooks, Zoho Books, Odoo
  • WhatsApp Business API for notifications and automated replies
  • CRM platforms: Salesforce, HubSpot, Zoho CRM
  • ZATCA Phase 2 (e-invoicing) for the Saudi market

How we work

  1. 01

    Define the integration and the flow

    Understand the data that has to flow between systems, identify the source of truth, draw the flow.

  2. 02

    Keys and registration

    Help you register and obtain API keys from providers, explain verification requirements.

  3. 03

    Build and sandbox testing

    Write the integration in the sandbox environment first, with retry logic and clear logging for provider errors.

  4. 04

    Launch and monitoring

    Production launch with automatic alerts on any failure and a dashboard for request count and error rates.

Technologies we use in this area

REST APIsWebhooksOAuth 2.0Queue workersSentry

Frequently asked

Yes. We implement Phase 2 e-invoicing (the live ZATCA integration) for Saudi systems, including QR code, electronic signing, and the clearance/reporting flow.

A standard gateway (Mada/HyperPay/Tap) typically takes 1-2 weeks from start to launch, including failure-scenario tests and tokenisation. A custom integration (multi-merchant, split payments) may need 3-4 weeks.

We build automatic retry logic with exponential backoff, a queue to defer failed requests, and immediate alerts on Slack/Email. The system does not lose data even if the provider is down for hours.

Yes — any provider with documented REST APIs we can integrate with. We do a short assessment before signing to confirm the requirements (rate limits, scope, sandbox).

Got a project in mind?

Answer 5 questions in 3 minutes and we'll come back with an initial estimate within a business day.

Start your project Or book a consultation