Skip to content

Engineering services for software that has to work.

Seven capabilities covering a system end to end — the interface your customers use, the services behind it, the data underneath, and the infrastructure it all runs on.
Pricing

How engagements are priced

Every engagement is quoted in writing before any payment is taken. All fees are quoted and charged in USD, and the scope, deliverables and payment schedule are agreed in a proposal or statement of work that you sign before work begins.
  • Project

    Fixed fee, billed against milestones

    from $6,000USD

    A defined scope with agreed deliverables, priced as a whole and invoiced as milestones are completed and accepted. A deposit reserves delivery capacity and covers discovery and architecture.

    Best for: A system with a clear outcome — a storefront, an ERP module, an AI workflow.

  • Retainer

    Monthly, cancellable with 30 days' notice

    from $3,500USD per month

    An agreed block of engineering capacity each month for ongoing development, maintenance and support. Billed monthly in advance, with a written summary of what the time went into.

    Best for: A live system that needs continuous work rather than a one-off build.

  • Consulting

    Fixed fee per engagement

    from $750USD

    Architecture reviews, code reviews and technical assessments delivered as a written document and a working session. Scheduled after payment, with the output delivered to an agreed date.

    Best for: A team that already has a system and needs an honest second opinion.

Currency. All fees are quoted and charged in USD. Your bank or card issuer may apply its own conversion rate or cross-border fee.

Payment. Invoices are issued by Rashid LLC and processed securely by Stripe. Card details are never collected or stored by us.

Taxes. Fees are exclusive of any taxes or duties, which are the client’s responsibility where applicable.

Cancellations and refunds. Covered in full by our Refund & Cancellation Policy and Service Delivery Policy.

Process

How an engagement runs

Five stages, each with a defined output. You always know what is happening, what comes next, and what you will have at the end of it.
  1. 01

    Discovery

    Understand the business problem before proposing a technical one.We start with how the work happens today — the process, the people involved, the systems already in place, and what specifically is failing. Scope, constraints and success criteria are agreed in writing before any estimate is given.

    You receive
    • Requirements summary
    • Scope and constraints
    • Success criteria
    • Indicative timeline
  2. 02

    Strategy & Architecture

    Decide the system design, stack and sequence — and write it down.Data models, service boundaries, integrations and infrastructure are designed up front. Technology choices are made against your team and your constraints, not our preferences, and the reasoning is documented so it can be challenged.

    You receive
    • System architecture
    • Data model
    • Technology decisions
    • Delivery plan
  3. 03

    Design & Development

    Build in reviewable increments you can see working.Interface design and implementation proceed together in short cycles. You get access to a working staging environment from early on, and a regular written update — so progress is something you observe rather than something you're told about.

    You receive
    • Interface designs
    • Working increments on staging
    • Code review and tests
    • Regular progress updates
  4. 04

    Testing & Deployment

    Ship through a pipeline, not by hand.Automated tests, staging verification and a repeatable deployment pipeline come before launch. Monitoring, logging and rollback are in place on day one, along with the documentation your team needs to operate the system.

    You receive
    • Automated test suite
    • CI/CD pipeline
    • Monitoring and alerting
    • Technical documentation
  5. 05

    Ongoing Support

    Stay available after launch, on terms agreed in advance.Software needs maintenance: dependency updates, infrastructure changes, new requirements. We offer continuing support arrangements, and where a client would rather take ownership internally, we hand over a documented codebase and help their team get up to speed.

    You receive
    • Support agreement
    • Maintenance and updates
    • Feature iterations
    • Handover documentation
Next step

Tell us what you're trying to build.

Send over the problem, the constraints and the timeline. We'll respond with an honest assessment and a suggested approach.

Within 1–2 business days · Working with clients in the United States and internationally