What we do
Services
Tensorway LLC builds, repairs, and maintains the data extraction and integration systems that keep operations, research, and analytics teams supplied with usable information. Every engagement is scoped in writing, quoted at a fixed price in USD, and delivered with source code your team owns and can run without us.
Pipeline Repair
Starting at $250 USD · delivery in 3–7 business days
What this is
You already have a data extraction job running in production, and it has stopped returning what it used to. Pipeline Repair is a focused diagnostic and fix engagement: we reproduce the failure against the live source, trace the root cause — restructured markup, a moved or renamed endpoint, a broken pagination or session flow, a field that changed shape — and repair the code you already have.
We work inside your existing stack rather than replacing it. Your language, your repository, and your deployment target stay the same, so the fix lands without a migration project attached to it.
Typical timeline
3–7 business days from the point where scope is agreed and repository or environment access is in place. If the diagnostic stage shows the problem is larger than a repair — for example, the source no longer publishes the data at all — we tell you before any further work is billed.
What you get
- Corrected source code, delivered as a patch or a pull request against your repository
- A written diagnostic report explaining what broke, why it broke, and how the fix addresses it
- Short documentation covering the components that changed and how to run them
- Field-level verification against a sample of live records, so you can confirm output quality before you rely on it
- 14 days of post-delivery support for questions and follow-up adjustments within the agreed scope
Good fit if…
- Your extraction job ran reliably for months and recently began returning empty, partial, or malformed records.
- The developer who wrote it has moved on and nobody currently on the team owns the code.
- You need the system you already paid for working again, not a rewrite you did not budget for.
Custom Data Pipeline
Starting at $750 USD · delivery in 7–14 business days
What this is
You need a dataset that nobody is currently delivering to you, and you want it arriving on a schedule instead of being assembled by hand. We design and build the extraction and integration pipeline end to end: source review, field mapping, scheduling, retry and error handling, validation rules, and delivery into the destination your team already uses — a database, an object store, a spreadsheet, or an internal API.
The deliverable is infrastructure, not a one-off export. It is written to be read by other engineers, structured so a single source change touches a single place, and handed over with everything needed to run it in your own environment.
Typical timeline
7–14 business days from the agreed scope, depending on the number of sources and the complexity of the destination system. Projects with several sources are split into checkpoints so you can review real output partway through rather than only at handover.
What you get
- Complete source code, organized for maintenance and written in Python or your team's preferred stack where that is practical
- Deployment instructions for your environment, covering configuration, credentials handling, and scheduling
- Technical documentation describing the architecture, the field mapping, and how failures are handled
- Validation checks and structured logging, so anomalies surface before they reach anything downstream
- A handover walkthrough with your engineers, plus 14 days of post-delivery support
Good fit if…
- Someone on your team is collecting this data manually today and the volume has outgrown that arrangement.
- You need consistent structure and scheduled delivery, not a single export that is stale within a week.
- You want to own the code outright rather than depend on continued access to a closed platform.
Monthly Maintenance Retainer
$400 USD per month · ongoing, month to month
What this is
Public data sources change without notice. Markup is restructured, endpoints move, fields are renamed or quietly dropped, and a pipeline that ran cleanly last week starts producing thinner output this week. The retainer keeps someone watching so that problems are found by us rather than by whoever opens the dashboard on Monday.
We monitor the pipelines named in the agreement on a defined schedule, investigate failed and degraded runs as they appear, and update the code when a covered source changes. Retainers cover systems we built as well as systems we have repaired and taken over.
Typical timeline
Retainers run month to month and are billed monthly in advance. Coverage starts on the date the first payment clears, and either side may cancel before the next billing date. The Refund & Cancellation policy sets out exactly how cancellation and any refund is handled.
What you get
- Scheduled monitoring of the covered pipelines, with alerting when a run fails or output falls outside expected bounds
- Priority response: issues reported under an active retainer are taken up ahead of new project work
- Code updates when a covered source changes structure, within the scope set out in the agreement
- A written monthly status report covering run health, incidents, and every change made that month
- A named point of contact by email for the duration of the agreement
Good fit if…
- A pipeline feeds a report, a product, or a process that people rely on daily or weekly.
- You have no in-house engineer available to respond when a source changes without warning.
- You would rather hold a predictable monthly line item than approve emergency work at short notice.
How an engagement runs
The same four steps apply to every project, whether it is a repair or a build from scratch.
- 1
Scope
Write down what you need and what the data is for. We reply in writing with questions until the scope is unambiguous. No call is required, and everything agreed stays on record.
- 2
Fixed quote
You receive a fixed price, a list of deliverables, and a delivery date. Payment terms are 50% upfront and 50% on delivery, in USD. If the scope does not change, the price does not change.
- 3
Build
We develop and test against the live source until the output matches the agreed specification. Progress is reported in writing, so you know the current state without having to ask.
- 4
Delivery + 14-day support
You receive the source code, the documentation, and the deployment notes. For 14 days after delivery we correct any defect in the delivered work at no additional cost.
Payment terms
- All prices are quoted and charged in United States dollars (USD).
- Project work is billed 50% upfront and 50% on delivery. The upfront payment confirms the booking and reserves the delivery window; the balance is due when the deliverables are handed over.
- The Monthly Maintenance Retainer is billed at $400 USD per month, in advance, for each month of coverage.
- Two rounds of revisions are included in every project engagement, covering adjustments within the agreed scope. Work that falls outside that written scope is quoted separately before it begins.
- Published prices are starting points. The figure in your written quote is the figure you pay for the work described in it.
- Invoices are issued by Tensorway LLC, New Mexico, USA. Billing questions go to billing@tensorway.net.
Full commercial terms are set out in the Terms of Service, the Refund & Cancellation policy, and the Delivery Policy.
Start with a scoping conversation
Tell us what the source is, which fields matter, and where the output has to land. We read every message ourselves and reply with an assessment and a fixed quote, normally within two business days. If the work is not a good fit for us, we will say so plainly rather than quote for it.