Case study · Marketplace
MotoSkelbimai
Build the marketplace.
Reuse the work behind it.
A motorcycle community needed more than a Facebook feed. The founder built a searchable marketplace with ChatGPT—and used Norbix for its data, seller accounts, email engine and ready back office.
- Norbix supplies
-
Data · Taxonomies · Membership
Email · Operating workspace - Built with
- Next.js + ChatGPT
Norbix CLI - Deployment
-
Norbix Managed Service
Founder-owned integrations - Project stage
- Public
marketplace
Further integrations in progress
The marketplace
The operating workspace
What the founder could build
A place to discover.
A place to sell.
A way to run it.
- 50
- source-verified ads in the launch catalogue
- 4
- shared catalogue taxonomies
- 13
- custom email templates, each in LT + EN
- 1
- existing back office reused to operate the marketplace
20 October project baseline. Counts describe catalogue content and configured tools, not customer adoption or measured development savings.
The idea → the journey
Keep the community.
Give it a better way to buy and sell.
A Facebook post gets buried. A marketplace gives each ad a place, useful filters and an owner who can return to manage it. That meant building the whole journey—not just a grid of bikes.
- 01
Find a bike
Buyers filter structured listings instead of scrolling through social posts.
Database + Taxonomies - 02
Post an ad
A seller can start as a guest. The private email connects the ad to its later owner.
Data + Membership - 03
Review it
The founder checks submissions in Norbix and decides what goes public.
Cloud workspace - 04
Come back
The tested email-claim flow lets the seller sign in and manage the ad on another device.
Email + Membership
The Norbix approach
One custom website.
A backend already equipped to run it.
The founder’s work went into the rider experience and marketplace rules. Norbix provided connected tools for the records, accounts and messages, plus a workspace to operate the product from the start.
Inside this project Turn a post into something a buyer can find.
Motorcycles, scooters, ATVs and parts need more structure than a caption.
The founder defined the listing model in Norbix. The custom website uses those records to show categories, filters and useful cards. The same backend also holds the directory, community entries and events.
- ✓Collections and a visual schema editor
- ✓Required fields and typed listing details
- ✓Project APIs for the custom website
A separate schema-management interface and record editor. The team could define its model and move on to the buying experience.
The listing schema
A catalogue riders can actually narrow down.
Custom search and filters, using the shared listing data.
What the buyer sees
One brand name.
Everywhere it matters.
A useful filter starts with consistent choices behind the form.
Categories, makes and conditions are managed as shared taxonomy terms. A seller’s selection and a buyer’s filter refer to the same catalogue choices. The founder can maintain them in Norbix as the marketplace grows.
- ✓Editable shared terms
- ✓35 brands in the captured catalogue
- ✓One source for forms, imports and filters
Building a taxonomy editor and maintaining separate brand lists across the application.
Shared brand choices
Build the storefront.
Skip the second admin app.
Every submitted ad still needs someone to decide if it belongs on the site.
The founder chose the existing Norbix Cloud workspace to inspect records and publish, reject or archive them. There was no need to create another website just to administer the first one.
Norbix Membership supplies account services. The application adds the marketplace’s ownership and revision checks: posting as a guest, signing in with the matching email and explicitly claiming an ad.
A custom back-office application and its separate administrator account system. Product-specific seller and publication rules stay in the application.
The operating workspace
Give sellers a way back to their ad.
A guest should be able to post now and manage the same ad later, on another device.
The application creates a Norbix transactional campaign for the ownership email. Norbix combines the template with the founder’s AWS SES integration. The seller follows the private link, signs in with the matching email and confirms the claim.
- ✓13 custom templates in Lithuanian and English
- ✓Transactional and marketing campaign tools
- ✓Email delivery through the founder’s SES account
Building a template manager, campaign tools and provider integration from scratch. The team wrote the claim’s security rules and reused the email engine.
The cross-device claim flow and manual review delivery were tested in the SES sandbox. Templates for other listing events are prepared; SES production access and native automatic event delivery remain unfinished.
The email engine
The agent works on the product’s actual backend.
ChatGPT helped build the custom website. The Norbix CLI connected that work to a real project.
The agent could inspect the project’s schemas and available operations, prepare changes and check the results. The founder chose permissions, providers and publication rules.
The same backend holds an editable source registry for a local event-discovery workflow—so the product can support ongoing operator work as well as the public website.
A connected project the coding agent could work with, instead of disconnected snippets to wire together by hand.
Event discovery runs on a local computer/session. It is not presented as a hosted Norbix agent.
Connect the coding agent
The difference Norbix made
More work on the marketplace.
Less work building tools to run it.
The clearest saving is a second admin product the founder did not have to build. The data tools, membership services and message engine also came ready to configure for this project.
Reused from Norbix
- Collection, schema and taxonomy management
- A record-administration workspace for the founder
- Membership identity and account services
- Template, campaign and email-provider integration tools
- CLI access for authorised agent work
Built for MotoSkelbimai
- The marketplace design, search and seller forms
- Guest claims and product-specific ownership checks
- Moderation, public-data boundaries and version checks
- Source research, import logic and release validation
Development hours saved were not measured. This story shows the specific systems reused and the custom work that remained.
The public catalogue and Norbix operating workspace are working. Email evidence is sandbox-tested. Automatic native email handoffs, direct device uploads, real payment settlement and Norbix App push are not claimed as finished. Screens and inventory show the 20 October baseline; later renewal and advertising extensions are outside this walkthrough.
Your next product
Build what makes your product yours.
Start with the backend tools
behind it.
Give your web app and coding agent connected capabilities for data, users and messages—and a workspace to manage them.