Skip to content
GraniteBolt, Home

The internal tool your team keeps asking for, built to last.

When the spreadsheet has become the system, or the ERP is missing one screen, a small piece of custom software pays back quickly. We build a focused first version: one core workflow, clear roles, an audit trail, and a codebase your team or ours can keep extending.

What we build

  • 01

    Customer portal

    Customers see their orders, shipments, invoices and documents, and raise requests, without emailing your team.

  • 02

    Operations dashboard

    The numbers managers ask for every morning, from the systems you already have, with a click through to the record.

  • 03

    Spreadsheet replacement

    The shared spreadsheet that runs a process becomes a small app with validation, roles and history.

  • 04

    ERP or CRM extension

    One missing screen, report or approval step, added through the system’s supported extension points.

  • 05

    Partner or agent portal

    Agents, suppliers or branches submit and track work in one place, with permissions per company.

  • 06

    Back office for your product

    Admin tools, support views and bulk actions for a team that has outgrown editing the database directly.

What you receive

  1. 01A numbered scope: users, roles, the core workflow and its screens
  2. 02The application in your cloud, with sign-in and role-based access
  3. 03An audit trail of who changed what, and when
  4. 04Import of your existing data from the spreadsheet or system it replaces
  5. 05Automated tests, CI, and acceptance testing with your team
  6. 06Handover docs, a recorded walkthrough and 30 days of fixes

Stack

A deliberately mainstream stack, so any competent engineer can maintain it after us.

  • TypeScript
  • Next.js
  • PostgreSQL
  • Supabase
  • Odoo, HubSpot, Zoho and Salesforce APIs
  • AWS

Typical timeline

Internal tool or portal, first version · 4-6 weeks
  1. 01Flows and roles
  2. 02Data model and access
  3. 03Build
  4. 04Your team tests
  5. 05Rollout

Phases are typical. The date in your quote is the one we commit to.

How we scope it

A written fixed quote within 48 hours of your first message or call.

  • Internal tool or portal, first version

    One core workflow, a few roles

    4-6 weeks

  • ERP or CRM extension

    One screen, report or approval step

    2-4 weeks

What shapes the quote

  • More than one core workflow, or many roles
  • Integrations with several systems
  • Data migration from messy or multiple sources
  • Offline use, several languages or several branches
  • Compliance needs such as audit exports

Ways of working

Most engagements are fixed-scope projects: numbered deliverables, a fixed price and a fixed date, all in writing before work starts. Product builds run as focused sprints with a working demo every week. After handover, Run keeps a system monitored, updated and improving month by month. The first call settles which one fits, and the quote states it in writing.

The AI angle

Add an assistant to the tool

Search across your records, answers over your SOPs, or a drafting step inside the workflow, with the same permissions as the rest of the tool.

See AI solutions

Questions about this service

Why not buy an off-the-shelf tool?

Often you should, and we will say so on the first call. Custom software earns its place when the process is your advantage, or when three tools and a spreadsheet cost more than one small app would.

What is in a first version?

One core workflow end to end, sign-in and roles, an audit trail, data import and deployment. Everything else is listed as a next phase, so the first version ships on its date.

Can you extend Odoo, HubSpot, Zoho or Salesforce?

Yes, through their supported APIs and extension points, never by patching their core. The extension lives in your repository and survives their upgrades.

Who can maintain it after you?

Any competent TypeScript engineer. The stack is mainstream, the repository has tests and docs, and the walkthrough is recorded. Or keep us on Run.

  • API and system integrations

    Your systems agree with each other, with retries, logs and alerts built in.

    Typical
    2-4 weeks

    See how we build it

  • Web apps and SaaS MVPs

    A first version of your product, live with real users on a fixed date.

    Typical
    20 business days

    See how we build it

  • Business automation

    The copy and paste between your tools, done by software that tells you when it fails.

    Typical
    1-2 weeks

    See how we build it

Tell us what you need built.

Describe it in plain words. Within 48 hours you have a written fixed quote and a delivery date.

A written, fixed quote within 48 hours.

Or write to hello@granitebolt.com

Your time and ours

Calls seven days a week

  • Beirut

  • Dubai

  • Riyadh

  • Doha

  • Kuwait City

  • Manama

  • Muscat

  • Cairo

  • Berlin

  • London

  • New York

Beirut shares the working day with Dubai, Riyadh, Cairo, Berlin and London, and the afternoon overlaps the New York morning.