Warmth with working clarity
Neutral surfaces and original campaign imagery create character. Consistent spacing, restrained category colors, and clear actions keep the dense partnership views readable.
Dayrate
Live product · Independent Noerong product
A considered workspace for the business of being creative: partnerships, deliverables, recorded payments, and an editable media kit.
IndustryCreator partnerships and media kits
AudienceIndependent creators, brand collaborators, and developers building creator tools
Studio roleProduct strategy, art direction, interaction design, frontend development, testing, and deployment
Released2026
The product
Built around the
actual workflow.
A partnership begins as a conversation, becomes a brief, then turns into dated deliverables and a payment to record. Dayrate brings those moments together with the creator's next introduction: an editable media kit. I designed and built this independent Noerong product around a fictional creator studio. Its brands, audience figures, and financial amounts are sample data, not client results.
The design thinking
A point of view,
in every detail.
A creator's working tools should feel connected to their creative identity. Dayrate balances expressive art direction with the quiet clarity of a useful operational workspace.
One record, several useful views
The pipeline, calendar, and earnings summary share campaign data. Each view emphasizes a different decision without asking the creator to re-enter the same information.
A kit ready to leave the workspace
The editable profile becomes an editorial media kit. Its print layout removes navigation and private campaign information, producing a focused one-page introduction.
Product walkthrough
See the complete
decision workflow.
A narrated tour of the connected creator workflow, including partnerships, calendar, recorded earnings, the printable media kit, and portable backups.
1600 × 1200 video · 2 minutes 42 seconds · Voice-over · No subtitles
Product approach
Less friction.
More clarity.
Warm neutral surfaces, precise typography, soft category colors, and original synthetic campaign artwork give the workspace a distinctive identity. Working screens prioritize the next action; the media kit carries the same language into an expressive editorial composition. Shared typed records connect the views. Short entrance sequences and smooth navigation respect reduced-motion preferences, while keyboard controls and visible recovery states support practical daily use.
Core system
What it
brings together.
From first conversation to final deliverable
Create and edit partnerships with a brief, fee, contact, stage, notes, and deliverables. Switch between a visual grid and pipeline, search, and filter. Campaign changes feed the surrounding overview and progress summaries.
A calendar connected to the work
Review deliverables in a monthly view, open the campaign behind a date, and mark work complete. Download an ICS snapshot for another calendar. Exports are portable files, not live synchronization.
An introduction with your point of view
Edit the creator profile, audience figures, and collaboration packages. Preview the media kit and print a focused one-page A4 PDF. Navigation and private partnership records stay out of the printed output.
Recorded amounts, clearly explained
Review entered fees, received amounts, outstanding balances, and work by category. Payments exceeding the campaign fee are rejected. These are manual records, not bank-confirmed payments or recognized revenue.
Portable data and considered recovery
JSON backups validate structure, dates, amounts, identifiers, and local image paths before replacement. Oversized imports are rejected, corrupt data is preserved until a recovery choice, and blocked writes show visible feedback. CSV exports escape spreadsheet-sensitive content.
Inside the product
The work, in detail.
Open any image for its full-size view. Sample records illustrate product behavior, not client performance.
Architecture
Why these
decisions.
Product designReactTypeScriptVite
React, TypeScript, and Vite power seven views. CSS handles responsive layouts and motion, with typed records and a tested domain layer connecting campaigns, deliverables, profiles, packages, totals, and exports. LocalStorage persists the workspace in the current browser and origin. A Docker configuration and lightweight static server support the live Railway deployment.
Outcome and boundaries
What is built.
What comes next.
Delivered product
The release passed its production build, 13 domain tests, and 19 browser tests. Responsive checks covered seven views at six widths from 360 to 1440 pixels, with no page-level overflow or page errors. Automated accessibility scans reported no violations in the configured WCAG 2 A/AA and WCAG 2.1 AA rules on seven desktop views. The A4 media kit was visually reviewed, and six smooth-scroll checks passed on the live Railway deployment. These are development checks, not a certification or measured customer outcomes.
Before a business launch
Deploy the source to buyer-owned static hosting or Railway. Workspace data stays in one browser and website origin; clearing site storage can erase it, and another device has separate data. Export JSON backups for recovery and transfer. This release has no accounts, backend, cloud backup, shared collaboration, payment processing, email delivery, social synchronization, image upload, or AI service. Amounts use USD. Extending those capabilities requires a separate scope.
Independently designed and built by Rongali Chaitanya at Noerong. Scope and acceptance criteria are agreed before a client implementation.
Make it your own
A foundation for your next build.
The $299 source kit includes React and TypeScript source, a production build, original synthetic campaign artwork, buyer guide, deployment files, and a commercial license for one end project. The $599 setup service includes the license, one brand configuration, one creator profile with up to three packages, one buyer-owned deployment, two scoped revision rounds, and handoff. Hosting, domains, new features, and ongoing support are separate. Workspace data stays in the current browser; accounts, cloud sync, shared collaboration, and payment processing are not included.
Next project
↗