Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Quarter April 1, 2026 – June 30, 2026

Q2 2026

Executive summary

Q2 was tri-bible.ai's earliest chapter: the Astro marketing site was scaffolded, the first end-to-end translation pipeline prototype ran Romans 1 into Hindi and Burmese, and the quarter closed with the Crowdin AI provider going live in production under the tri-bible.ai domain.

What's new

  • Change

    Scaffolded the Astro and Tailwind marketing site from scratch.

    Impact

    Established the technical foundation every later feature has built on.

    Next action

    Expand the site with real pipeline output, not placeholder copy.

  • Change

    Ran the first full TRI pipeline, translating Romans 1 into Hindi and Burmese.

    Impact

    Proved the multi-agent translation concept end to end for the first time.

    Next action

    Turn the working prototype into a public-facing example page.

  • Change

    Built the Bible reference parser and automatic YouVersion link injector.

    Impact

    Lesson content can now link to Scripture without manual hyperlinking.

    Next action

    Apply the linker to every future translated lesson.

  • Change

    Deployed the Crowdin AI provider to production and renamed the project to tri-bible.ai.

    Impact

    Ministries can now install tri-bible.ai as a live Crowdin translation provider, under its permanent brand.

    Next action

    Onboard our first pilot ministry onto the Crowdin integration.

Business impact

Every later feature — the Library, German and Turkish depth — builds on the site, pipeline, and Crowdin integration foundation laid this quarter.

Metrics

  • Languages with any pipeline output

    2(was 0) Up from last period

  • Site pages live

    1(was 0) Up from last period

  • Crowdin AI provider status

    Live in production(was Local prototype only) Up from last period

Risks

The pipeline had only been proven on a single short passage; scaling to full books and many languages was still unvalidated going into Q3.

Decisions needed

Leadership: decide whether to invest in scaling the pipeline to full books before or after building the public Library (resolved in Q3: both were pursued together).

Next Quarter

  • Launch the public Library page
  • Onboard our first pilot ministry onto the Crowdin integration

Key dates

No key dates recorded for this period.

In this quarter