Frequently asked questions.
Questions about timelines, tools, ownership, security, and how we work.
How long does a typical project take?
Most projects follow this timeline: Discovery Sprint (1–2 weeks), Build Phase (4–12 weeks depending on scope), and Operational Handoff (2–4 weeks). So from start to live is typically 2–4 months. Complex organizations with many data sources or legacy systems may take longer. We establish realistic timelines during discovery.
Do you work with our existing tools or replace them?
We work with what you have. We integrate with your existing ERP, CRM, warehouse system, accounting platform, and production systems. We don't force tool replacements. If you need a warehouse, we recommend industry-standard options (Snowflake, BigQuery, Redshift) based on your constraints. The focus is on building on top of what already exists.
Who owns the data after you leave?
Your team does. From day one, we document everything, establish ownership models, and train your people. At the end of the project, we hand over complete systems, runbooks, and escalation paths. You're not locked in. Your team should be fully capable of operating the systems independently after the operational handoff phase.
How does human review work with AI automation?
AI is best used for high-volume, rule-based tasks where exceptions are expensive. We build systems where AI handles the straightforward path and routes complex cases to your team. Every classification, triage decision, or summary is visible and reviewable. There's no black box. Your team understands exactly what the system did and can provide feedback to improve it.
How do you handle data security and privacy?
Security is built in from the start. We follow industry best practices: encryption in transit and at rest, role-based access control, audit logging, and regular security assessments. We comply with standard data protection regulations. Sensitive data stays within your infrastructure or approved cloud environments. We can discuss specific compliance requirements (SOC 2, HIPAA, GDPR) during discovery.
What kind of training does your team get?
We provide hands-on training covering system navigation, metric definitions, incident response procedures, and how to spot data quality issues. Training happens throughout the build phase and intensifies before go-live. Post-launch, we support the first month of operations and provide quarterly optimization reviews.
What support is included after launch?
Standard support coverage is Monday–Friday, 8:00 AM–6:00 PM Eastern Time, excluding U.S. federal holidays. We respond to critical issues (system down) within 30 minutes. High-priority issues get a 2-hour response. We focus on helping your team operate independently, not creating ongoing dependency.
How do you approach pricing?
Pricing is project-based, not per-user or per-month. We estimate during discovery based on scope, complexity, team size, and timeline. Typical data foundation projects range from $50K–$150K depending on the number of systems and data volume. AI automation projects are sized separately. We provide fixed estimates with change order processes for scope changes.
How much documentation do we get?
Comprehensive documentation is a core deliverable. For each system we build, you receive: metric definitions, transformation logic, pipeline documentation, runbooks for common incidents, escalation procedures, and team training materials. Documentation is written to be operational, not theoretical.
Does Rivetline replace your internal team?
No. We don't replace teams; we build systems that allow your existing team to work more effectively. Our goal is to handle complexity so your team can focus on strategy and decision-making, not manual data work. We train your people. We hand over ownership. You stay in control.
What if scope changes mid-project?
Scope changes happen. We discuss it with you, estimate the impact on timeline and cost, and update the project plan. Minor changes are absorbed within the project buffer. Significant scope additions require a change order and timeline adjustment. Everything is transparent.
Do you guarantee results?
We guarantee the systems we build work reliably and meet the specifications we agreed on. We can't guarantee business outcomes (cost savings, revenue impact) because that depends on adoption, execution, and factors outside our control. We give representative project outcomes, not promises. Our success metric is systems your team actually uses and trusts.
Didn't find what you're looking for?
Reach out directly. We're happy to answer more detailed questions about your specific situation.
Contact us