Proof

Useful proof is not a polished screenshot. It's the path from chaos to software you can operate and change after launch.

Our products

We develop our own products, too.

At Thinqcraft, we develop products for research teams and organizations preparing public tender bids. We combine product development with responsibility for keeping the software running.

Sondara study editor with an example single-choice question and branching settings. Fictional demonstration data.

Sondara

Research surveys from questions to responses.

Free research software for preparing questions and sessions, configuring branching, previewing studies and exporting responses to CSV. We develop and operate Sondara as an independent Thinqcraft product. It builds on open-source research software from Michigan State University.

Our work covers the researcher workspace, participant experience, technical modernization, deployment and operations.

Researcher accounts are available by invitation.

EaseYourDay bid workspace showing requirements, documents and outstanding submission blockers. Fictional demonstration tender.

EaseYourDay Tender Operations

A shared workspace for preparing tender bids.

A product for teams that regularly bid for public contracts. It connects opportunity discovery and qualification with requirements, documents, responsibilities and bid readiness review.

It helps preserve the connection between reviewed document versions and the package prepared for submission. The team remains responsible for final content, signatures and submission through the official channel.

Pilot scope is agreed with each team.

Proof across domains

Pressure, delivery, result

Marketplace sync

Marketplace operations and product synchronization

Tens of thousands of products, large vendor feeds and category changes were crossing channels with too much manual cleanup.

Result

Operations can see what moved, what changed and what needs attention before customers notice drift.

What shipped: Structured feed parsing, delta sync, taxonomy and parameter mapping, adapter-based marketplace flows and visible failure handling.

Explore the technical context
Structured knowledge

CMS, content platforms and knowledge systems

Expert content needed stable identity, multilingual structure and machine-readable meaning across public product surfaces.

Result

Knowledge behaves like a maintained product surface, not a loose pile of pages.

What shipped: Public projects such as 555 EUCRiders with JSON-LD, Turtle, Pagefind search, stable entities and multilingual publishing checks.

Explore the technical context
Modernization

Modernization, infrastructure and rescue work

The system still worked, but Rails, frontend tooling, queues and infrastructure made every change harder to price.

Result

The system can change again without turning every request into rescue work.

What shipped: Rails 8 upgrade work, React/Vite migration, SolidQueue and Action Cable flows, PostgreSQL tuning and Linux/NGINX/Puma cleanup.

Explore the technical context
More areas of experience

Practice, explained

The engineering decisions behind the proof.

Deeper notes on boundaries, risk and production habits that make the visible outcomes repeatable.

Read the technical notes
Architecture

A shared SaaS platform without a framework built in advance

How to prepare modular SaaS for future domains by sharing stable mechanisms without prematurely generalizing the business.

Architecture

An audit log is not the same as application logging

How to design audit history as evidence of a business operation rather than another table of technical messages.

Next step

Tell us where the pressure sits.

A rough outline of the workflow, system and constraints is enough to start.

Start a conversation