Case Study
We made Kurtsan's product catalog adjustable
A slow, manual catalog process became a system that makes life easier for the people doing the buying.
What we built
Kurtsan's product catalog ran on a slow system and largely by hand. Producing a PDF catalog was laborious and changing what a catalog covered was not easy. We replaced it with a system where products are maintained in one place, catalogs are assembled to fit the need, and dealers can reach their own product lists.
- Project Duration
- 90 working days
How it ran before
The system was slow
Catalog work took long enough to be worth avoiding, which turned every small change into a job that got postponed.
PDF catalogs were slow to produce
Exporting the product catalog as a PDF was neither quick nor repeatable, even though it was the output the sales side needed most often.
The structure was rigid
Changing what went into a catalog, how much of it, and in what order was not straightforward. Every different request meant separate work.
The process ran by hand
From collecting product information to assembling the catalog, most of the chain was manual.
It surfaced less in AI search
Product information was not held in a shape that AI assisted search could read and weigh properly. When buyers searched through those channels, the products showed up less than they should have.
The modules we built
Product editing
One place where product information is entered and kept up to date.
Catalog builder
Where a catalog is assembled from selected products and exported as a PDF.
Catalog content settings
Where you define which information appears in a catalog, and how.
Dealer accounts
The sign-up and login flow dealers go through.
Dealer product lists
The list where a dealer sees the products assigned to them.
Detailed analytics
Reporting written inside the system rather than wired to an outside service.
How the system runs
- 1
Products are entered in one place
Product information is defined and kept current from the product editing screen.
- 2
Catalog content is configured
The catalog content settings decide which fields appear, and how.
- 3
A catalog is produced
A catalog is assembled from the selected products and exported as a PDF.
- 4
A dealer opens an account
Dealers sign up through the membership flow and log in.
- 5
The dealer sees their own list
Products assigned to that dealer appear in the dealer product list.
- 6
Activity is reported
The analytics written inside the system report usage and product activity.
Frequently asked questions
How long does a product catalog system like this take?
The Kurtsan project ran 90 working days. That range is realistic for a similar scope; more modules and more integration work push it out.
Does the catalog really come out as a PDF?
Yes. A catalog is assembled from the selected products and exported as a PDF. Making that quick and repeatable was one of the reasons the project started.
How do dealers get into the system?
They open an account through the dealer membership flow and see the product list assigned to them.
We already have a system. Does it have to be rebuilt from scratch?
No. Where something already runs, we extend it, integrate with it, or migrate it without stopping your operation.
Who owns the software?
You do. Ownership and confidentiality are written into the agreement before any work starts.
Facing Similar Problems?
If you need something along these lines on the catalog, dealer portal or product management side, let us talk about what can be done.
Average Response Time: 15 Minutes