ScaleForged

Forged here. Built to last.

An independent venture studio · Québec, Canada

The world’s knowledge.Products created here.

ScaleForged brings knowledge to Québec from the world’s great developer and research communities, open work and philanthropic initiatives.

Global knowledge converges on QuébecAn illustration of our ambition: learn from the world and develop intellectual property here. Arrows do not represent partners or existing transfers.
Global knowledge → value created hereAn ambition, illustrated.

We create products here, with the people here, with a clear commitment: keep the intellectual property we develop in Québec and Canada.

  1. 01Learn from the world
  2. 02Build with people
  3. 03Grow it here

One cycle. Orchestrated agents.

Twelve stages of software development, coordinated by specialized AI agents. People set direction, review results and approve each next step.

“The next version must earn its place.”

Define / Illustrative processStep 01 / 12

Voice

Turn the spoken need into a clear brief.

  1. Capture the need
  2. Write the brief
  3. Confirm together
AI agent
Listening agent
Output
Intent brief
Human approval
You confirm the need and the people it should help.
feedback returns
01

Define

02

Build

03

Learn

The targetUseful, accepted work

Explore a step

All 12 steps, in detail
  1. Voice

    Turn the spoken need into a clear brief.

    Output : Intent brief

    Human approval : You confirm the need and the people it should help.

  2. Plan

    Break the brief into steps and acceptance criteria.

    Output : Acceptance criteria

    Human approval : You set the priorities, limits and budget.

  3. Unblock

    Check for missing access, tools and information.

    Output : Access checklist

    Human approval : You authorize access and resolve the blockers.

  4. Design

    Sketch the workflow and its reversible choices.

    Output : Workflow sketch

    Human approval : You approve the workflow before construction.

  5. Build

    Build the smallest workflow that meets the brief.

    Output : First working draft

    Human approval : You try the draft and point out the gaps.

  6. Iterate

    Correct a gap, then compare both versions.

    Output : Revised workflow draft

    Human approval : You keep the correction or request another build.

  7. Test

    Test the workflow, errors and edge cases.

    Output : Test evidence

    Human approval : You inspect the evidence and send failures back to build.

  8. Review

    Have another agent examine the code and risks.

    Output : Independent review notes

    Human approval : You accept the review or request a correction.

  9. Ship

    Prepare a pilot and rollback plan before release.

    Output : Pilot release plan

    Human approval : You authorize release to the chosen audience.

  10. Measure

    Assess quality, time and full cost per accepted task.

    Output : Evaluation summary

    Human approval : You judge usefulness and choose what to improve.

  11. Listen

    Connect field feedback to the plan’s acceptance criteria.

    Output : Feedback priorities

    Human approval : You choose which feedback should reshape the plan.

  12. Repeat

    Bring the lessons into the next spoken brief.

    Output : Next cycle brief

    Human approval : You start another cycle or choose to stop.

02 /

The studio ecosystem

Distinct missions. One connected ecosystem.

Each product has a role. Shared capabilities move the whole studio forward.

Nota

Nota

Transform notarial services

Bring the client’s need closer to the notary’s decision.

Build an industry product where trust matters.

Beta
Tablix

Tablix

Make document work more useful

Turn RDPRM PDFs into structured documents a professional can verify.

Prioritize a concrete paid workflow with review in the loop.

Beta
SST Diamantex

SST Diamantex

Connect field work to prevention

Carry a worker’s observation into a reviewed action.

Apply the studio’s capabilities to teams’ real work.

Beta
PlainLedger

PlainLedger

Guide product decisions

Put each product’s indicators in context for better decisions.

A shared performance product for the whole portfolio.

Beta
Ursly

Ursly

Prepare the next generation

Explore more natural interaction through human senses and AI research.

An R&D product preparing the next iteration and its funding.

Research and development
Control Craft

Control Craft

Target near-term revenue

Turn places, passions and memories into art.

A commercial product to test sales, content and fulfillment. Revenue remains an objective.

Go-to-market proof of concept
Devanture

Devanture

Build the next way to shop

Bring together storefront experience, live 3D negotiation and commercialization.

One modular offering: standalone, as an intended Shopify alternative, or added to an existing store.

Modular platform in development

One commerce offering

  • Devanture · 3D storefront and 2D shopping
  • OfferDuel · Live negotiation
  • Ralika · Commercialization and customer relationships

Standalone platform · Add-on to an existing store

DealBox · A sub-project to test a market, its catalogue and recurring drops.

Connections describe the intended model. Integrations are qualified workflow by workflow.

03 /

Why we build

Technology moves forward. So should people.

Strengthen skills. Keep judgment human. Lighten the repetitive work to make room for what matters.

  • Family.
  • Free time.
  • Enjoyment.
Commitments to evaluate with each team, through real work.

The ScaleForged model

A proven venture studio model.

Founded in California. Replicated in Québec.

One shared studio. Multiple companies.

CREE8The same modelStudioCaliforniaQuébecCompaniesCREE8The same modelStudioCaliforniaQuébecCREE8The same modelStudioCaliforniaQuébec
Anthony Paquet

CREE8 · California

Anthony Paquet

Founder in California

3 yearsHead of Engineering

ScaleForged · Québec

The model replicated in Québec.
Founder-reported background

This background implies no employer endorsement and no transfer of customers, proprietary code or intellectual property. View the professional background

04 /

The studio advantage

Build once. Give the next venture a head start.

Every venture has its own identity. The shared foundation grows: tools, methods, structures and lessons learned.

A foundation to share

CPA & finance

Shared support.

Structure & agreements

Reusable foundations.

Code & tools

Fewer blank pages.

Know-how

Learn, then pass it on.

The know-how stays. The next project starts further ahead.

Inside the foundation

CPA & finance

Shared CPA support reported by the founder. The engagement, services and scope for each venture still need confirmation.

Structure & agreements

Structure and agreement templates adapted to each project. Rights, intellectual property and obligations are defined in their own agreements.

Code & tools

Software foundations, integrations, delivery tools and test cases reused where licences and rights permit.

Know-how

Methods, industry knowledge and field feedback: document what works to inform the next cycle, without sharing customer data by default.

Reuse respects the licences, rights and agreements of each project.

Measure useful work. Make room for people.

Explore an illustrative workday. Actual gains must be measured with the teams doing the work.

One possible workday

Same team. Less repetition. Time back.

  • Retyping deeds and forms2.5h
  • Chasing signatures and files1.5h
  • Client calls and meetings2h
  • Reviewing deeds2h
  • Time back0h
Team size: unchanged

Repetitive work: 4h / 8h

Illustrative scenario, not a measured result. Each pilot must assess workload, quality, skills and well-being with the team before claiming a gain.

The next loop starts with you

An industry to understand. Something worth building.

An idea or a partnership in mind? Let’s talk. Investment amount, structure and timing are open for discussion, based on mutual fit, investor involvement and available capital.

Build with us