Bridgeline Digital, Inc.: cost of revenue

What this measure means

Costs attributed to goods produced and sold and services provided during the period. This is not the sum of every operating expense.

Exact concept: us-gaap:CostOfRevenue. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2009-10-01 to 2018-09-30. The SEC response was captured on 2026-09-20.

This selected history ends more than two years before capture. Do not treat its final value as a current balance or current annual result. More recent filings may use another accounting tag; inspect the filings before drawing conclusions about the company.

Selected filing history

Related financial histories

• Bridgeline Digital, Inc.: total assets
• Bridgeline Digital, Inc.: total liabilities
• Bridgeline Digital, Inc.: stockholders equity
• Bridgeline Digital, Inc.: cash and cash equivalents
• Bridgeline Digital, Inc.: net income or loss
• Bridgeline Digital, Inc.: operating cash flow
• Bridgeline Digital, Inc.: capital expenditure payments
• Bridgeline Digital, Inc.: revenue
• Bridgeline Digital, Inc.: contract revenue excluding tax
• Bridgeline Digital, Inc.: financing cash flow
• Bridgeline Digital, Inc.: investing cash flow
• Bridgeline Digital, Inc.: retained earnings or deficit
• Bridgeline Digital, Inc.: basic weighted-average shares
• Bridgeline Digital, Inc.: diluted weighted-average shares
• Bridgeline Digital, Inc.: basic earnings per share
• Bridgeline Digital, Inc.: diluted earnings per share
• Bridgeline Digital, Inc.: income tax expense or benefit
• Bridgeline Digital, Inc.: net property, plant and equipment
• Bridgeline Digital, Inc.: share-based compensation expense
• Bridgeline Digital, Inc.: operating income or loss
• Bridgeline Digital, Inc.: current assets
• Bridgeline Digital, Inc.: current liabilities
• Bridgeline Digital, Inc.: current accounts payable
• Bridgeline Digital, Inc.: goodwill carrying amount
• Bridgeline Digital, Inc.: net finite-lived intangible assets
• Bridgeline Digital, Inc.: net current accounts receivable
• Bridgeline Digital, Inc.: operating expenses
• Bridgeline Digital, Inc.: gross profit
• Bridgeline Digital, Inc.: research and development expense

Inspect the source

Entity

Bridgeline Digital, Inc. / CIK 0001378590

Captured

2026-09-20T07:57:56.616Z

SEC response SHA-256

dade7dc4508f206450a3510ddce6b34fa7ebc97365b3e247d1867bc00a944ed6

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

• Get an API key and run your first validation
• Connect the MCP server to your coding assistant
• Inspect the ALPHAC engine on GitHub
• Read the MCP server source and integration examples

import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001378590.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))