GoSeedly Tattoo Studio Kit
Artist books in near-black, with a four-square approval stepper, tally marks for sessions completed of sessions planned, and one red flag for a deposit that has passed its hold window. Stencil keeps every consult, deposit, design round and session your studio records in one connected workspace.
YOUR STENCIL ARTIST BOOKS
01 — BOOKS
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / BooksEach column is headed by the artist, their style label and the books-open or books-closed state you recorded. Every card carries the client, the piece, the placement and size, four ink squares for the recorded steps, the design round count and a session tally.
02 / PiecesEvery piece with its artist, placement and size, the four recorded steps, what it is waiting on next, the design rounds and the sessions completed of planned.
03 / ConsultsRecorded consultation dates newest first, with the artist, the follow-up state and the deposit that was taken. Consultation dates are values you record, not appointments.
04 / DesignsEvery design round still waiting on the client, longest waiting first, with the round date and the note that went with it.
05 / SessionsRecorded session rows by date with the artist, the stage of outline, shading, color or touch-up, the hours recorded in quarter-hour steps and whether the session was held.
06 / Touch-upsRecorded touch-up sessions, then the healed check-ins whose recorded date has arrived, each with the last session that was held.
07 / InsightsPiece counts by the step they are waiting on, each opening the pieces behind the number, with the deposits past their recorded hold window and the hours recorded across held sessions.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore 12 fictional pieces across three fictional artists, one with closed books. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
One contact-linked record follows one tattoo piece: client label, artist, placement, size and style labels, the ink plan, reference notes as plain text, the age verified and consent-on-file flags with the dates they were checked, the consultation date and follow-up state, the deposit amount with its date, applied flag and hold window, the quoted estimate, the planned session count, the healed check-in date, design rounds, sessions and an editable checklist. Artists are a separate per-workspace record set with a name, a style label and a books-open flag.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit studio name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected piece creation, edits, the artist record set and resource setup. They preserve native account permissions, unrelated custom fields and row history, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
The four stepper squares, sessions completed of planned, days since the deposit, the stalled flag and the healed check due flag are derived from values you record. The kit is not a booking or scheduling engine: a session date is a recorded value and nothing reserves an artist’s time or prevents a clash. It does not process payments or collect deposits; the deposit is a recorded amount. It is not a consent or age verification service: the flags record only that studio staff checked the item on the date beside it, and no identity document is stored. It stores no images, flash or reference artwork, only plain reference notes. It gives no aftercare advice and records only that your own handout was given. It sends no client messages.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Stencil retains its application frame across the kit views and native CRM tools in the same signed-in account, in one near-black theme with no accent hue. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.