Skip to content
How we work

Our process and billing.

See how we scope, build, and support your solution, and what we bill for along the way.

DiscoveryGoalsScopePlanDeliveryBuildTestHandoff

Two phases. Six steps.

Discovery

  1. Gather and assess

    We meet with you and review your systems to understand your challenges, goals, and business needs.

  2. Gaps and engineering

    We build a roadmap and provide documentation and estimates. Depending on complexity, we may run a gap analysis to refine requirements or use a retainer or small agreement to cover initial engineering.

  3. Demonstrate capability

    For complex projects, we build a Minimum Viable Product (MVP) or Proof of Concept (POC) to demonstrate feasibility and impact before you commit to a full build.

Delivery

  1. Implementation and testing

    We design, build, and deploy the solution into your existing systems and workflows. We test it for reliability and check that it meets your goals.

  2. Training and enablement

    We provide tailored training, tools, and detailed documentation so your team can use and support the solution.

  3. Support and improvement

    We provide ongoing support by email or phone under your SLA, with enhancements, new features, and system reviews as your needs evolve.

How billing works

The billing model depends on the scope of the work and whether it needs ongoing hosting or support.

Time-Based

For evolving or unknown requirements, ongoing requests, out-of-scope changes, and maintenance updates.

  • Billed on actual time spent
  • Best-effort estimates available on request

Fixed

For well-defined requirements with a clear scope and fixed deliverables, or configuration of Rubi SaaS products.

  • Billed on quoted time or effort
  • Can be combined with Time-Based billing for variable work

Recurring

For Rubi SaaS products and hosting custom integrations, data warehouses, and automation solutions.

  • Includes hosting, monitoring, and support
  • Includes in-scope bug fixes

Billing FAQ

When we don't bill

  • Initial scoping of smaller projects (no engineering required)
  • Demonstrating existing products or pitching ideas
  • Proactive work without prior authorization (unless there's an agreed arrangement for proactive work)
  • Fixing errors or bugs that are in scope of a previous project
  • Administrative meetings and routine non-working status calls

When we bill

  • Gap analysis
  • Engineering work for projects or proofs of concept (may be waived based on project and reusability)
  • Research and insight requests
  • Creating or providing documentation
  • Solution updates required due to 3rd-party changes (APIs / services)
  • Problem-solving meetings
  • Configuring environments and setting up workspaces to provide services

Talk through your project