Questions about Lenso

Lenso is client workflow software for product photography studios. It keeps a website request or studio-entered referral, product and shot requirements, client review, requested changes, approval, optional invoice, and final files attached to the same job.

• See how Lenso works for studios

Lenso is built for commercial product photography studios that manage recurring client work with products, SKUs, shot lists, proofs, review decisions, and final-file delivery.

It is not positioned as a general tool for wedding, portrait, event, or hobby photography, and it is not an enterprise creative-operations suite.

No. Studios bring their own clients. Lenso does not list studios, match brands with photographers, sell leads, or book photography services on the studio's behalf.

Not necessarily. Lenso connects the client-side job context. Studios can keep specialist tools for capture, editing, accounting, long-term storage, contracts, scheduling, or another part of their operation.

Lenso is not a full photography CRM, capture application, retouching application, crew scheduler, accounting system, or general digital-asset-management platform.

No. Lenso does not currently manage crews, call sheets, equipment, sets, product shipping, studio scheduling, or physical production logistics.

It keeps client requirements, product context, review decisions, and final-file delivery connected around the job.

No. Lenso hosts the structured request experience. A studio can link to it from its existing website or use the dedicated embed route when the current implementation and site security policy support embedding.

The requester confirms their email. The studio reviews the request, decides whether it is a fit, and chooses whether to convert it into a job and invite the client.

The request is not automatically accepted, quoted, scheduled, or turned into client work.

No. The studio controls conversion. Unverified requests cannot be treated as accepted work, and a request does not automatically become a job without the studio's action.

The studio can enter the work itself and use the same structured path. The website request is one entry point, not the identity of the whole product.

No. Start with one current or upcoming job. Bring over only the context needed to run that work.

Historical migration should be considered only when real customer demand justifies the setup effort.

A structured request or brief can collect contact details, products or SKUs, variants, required views, references, deadlines, output specifications, naming instructions, and other fields defined by the studio's current template.

The studio should review the submitted information rather than assuming it is complete or correct.

The reviewed product supports structured CSV and XLSX shot-list import. Use the latest in-product import template as the authority for accepted columns, formats, and validation rules.

The public shot-list template is a planning resource and may contain additional columns that do not map directly to the importer.

• Use the shot-list template

No. A job can begin with a public request, studio discovery, a referral, or information the studio already has. The studio can review, correct, and complete the structured record before it becomes the working brief.

AI Brief Assist can turn plain-language request text into a draft of structured fields on an enabled request form. The visitor or studio reviews the draft before it becomes part of the request.

It does not approve the request, make the studio's decision, run the job, or replace a person. The configured AI provider processes the text needed for the draft, so the current Privacy Policy and production provider terms apply.

• Read the AI Brief Assist guide
• Read the Privacy Policy

No. Lenso can preserve the brief, shot rows, proofs, comments, decisions, and final files. It does not currently certify color, crop, retouching, product truth, or compliance with every marketplace or retailer rule.

A qualified person still reviews the work against the current client and destination requirements.

• Use the quality-control checklist

No. The studio pays for the workspace. Invited clients use project-specific secure access, with no paid studio seat.

The studio invites the client by email. The client uses a time-limited magic link instead of creating a password-based studio account.

The link is an access credential. It can expire, be revoked, be replaced, or be resent according to the current project policy.

Depending on the job state and enabled features, a client can review the brief, view proofs, leave comments tied to the work, request changes, approve, view or pay an invoice, and download released final files.

The studio controls what is available and when final files are released.

Approval is a recorded decision attached to a named proof, version, or set. It gives the studio and client a clearer operational record.

The client agreement and applicable law define the legal effect of approval, silence, delivery, and acceptance. Lenso does not decide that legal meaning.

• Read the Terms of Service

The studio releases the approved final files through the job. Clients can download the files made available to them, and the product can support grouped delivery and manifest information where the current job uses those features.

The studio should test the actual delivery path and record what was released.

• Read the client-area guide

Yes. Client links are time-limited and can be revoked or replaced. A fresh link can be sent when the studio's policy and current job state allow access.

No universal permanent-access promise applies. A client can access the project covered by a valid link and the current release rules.

Access can expire or be revoked, and retention depends on the studio agreement, subscription state, storage, account status, and current Lenso policies. The client area is not a permanent cross-project asset library.

Not today. Repeat work is studio initiated. The studio can use prior requirements, decisions, and delivery context as a starting point, then review what is still valid for the new job.

Eligible new studio workspaces can start a 14-day trial without a card. Previous trial or paid-subscription history can affect eligibility.

• Review current plans and trial terms

Under the current default policy, the trial ends automatically when no payment method is added. The workspace does not silently convert into a paid subscription.

Current retention and deletion behavior is explained in the Privacy Policy and account settings.

• Read the Privacy Policy

Choose based on studio seats, storage, branding controls, and support. Job volume alone does not select a plan.

At the reviewed pricing contract, Starter includes up to 3 studio seats and 200 GB, Team includes up to 8 seats and 1 TB, and Scale includes up to 15 seats and 3 TB.

• Compare the current plans

Subscription checkout, plan changes, billing-portal access, storage packs, and other platform-billing mutations are workspace Owner actions. An Admin does not replace the Owner for subscription billing.

Yes. The current billing flow should show the selected plan, billing cycle, amount, and effective timing before confirmation.

Upgrades can take effect sooner, while a downgrade can be scheduled for the next billing period. The backend remains the authority for exact timing.

Existing files are not deleted merely because the included storage becomes lower. New uploads pause while the workspace is above its allowance.

A lower seat allowance can block new invitations until the workspace is within the current limit. Saved branding values can remain stored even when an unentitled control no longer renders.

All current paid plans include the studio name and logo on entitled public and client surfaces. Team and Scale add a custom accent color and the option to hide the Powered by Lenso footer.

• Review branding by plan

Not today. Lenso hosts the request and client area. Custom domains and studio-domain transactional email remain demand-gated rather than current product promises.

Stripe is optional for studio-client invoicing and online payment. A studio can use Lenso without connecting Stripe.

Lenso does not take a percentage of the studio's client invoice. Stripe processing fees and the connected Stripe account's terms can apply.

• Review payment and subscription details

At the reviewed pricing contract, Starter includes 200 GB, Team includes 1 TB, and Scale includes 3 TB.

• Read the storage guide

Existing downloads remain available, but new uploads are blocked while the workspace is over its current allowance. The studio can delete files, move to a plan with more storage, or use a storage pack when that add-on is configured and available.

Recurring 10 GB storage packs can be added from Billing when that add-on is configured.

The studio decides whether a refund for its photography services is due under the studio-client agreement. An authorized studio Owner or Admin can use a supported Lenso refund path when the connected Stripe configuration allows it.

Lenso does not decide whether the photography service was satisfactory.

• Read Refunds and Payment Disputes

No. Files are private by default and are made available through authenticated workspace access or project-specific client access.

A secure link is still an access credential and should be handled accordingly.

The reviewed product uses private S3-backed object storage and time-limited access URLs.

• Read about Lenso security

Stripe handles card entry and payment processing for Lenso subscriptions and optional connected client payments. Lenso does not store raw card numbers.

The workspace Owner can request an export through the current account tools. Account deletion uses a grace period and can be blocked while subscriptions, jobs, invoices, payments, or other required conditions remain unresolved.

The current Privacy Policy is the authority for retention, deletion, and individual privacy requests.

• Read the Privacy Policy

The reviewed product does not currently include built-in MFA, enterprise SSO or SCIM, customer-managed encryption keys, selectable data residency, SOC 2 certification, or ISO 27001 certification.

• Review current security capabilities and limits

When the optional feature is used, the text needed to draft structured request fields is sent to the configured AI provider. A person reviews the result.

The current Privacy Policy is the authority for AI data use.

• Read the Privacy Policy

Use the current reporting path on the Security page for a suspected vulnerability. Use the Status page for current service information.

• Report or review a security issue
• Check Lenso status

Lenso has Owner, Admin, and Member roles. The Owner has full workspace authority and is the only role that manages the Lenso subscription.

Admins can manage many workspace, project, client, and team actions. Members work on the projects they are allowed to see, and a workspace can limit Member visibility to assigned projects.

• Read the team-role guide

The reviewed product includes brief-completion reminders, approval-pending reminders, invoice reminders, and a daily activity digest when the related settings and job conditions apply.

Lenso does not currently provide a general if-then automation builder.

Lenso does not currently publish a guaranteed public support-response SLA. Use the Contact page for product, account, subscription, billing, or technical questions.

• Contact Lenso

Use the Help Center for setup, requests, briefs, client access, approvals, invoices, storage, team roles, onboarding, and AI Brief Assist.

The FAQ gives concise product boundaries. The Help Center should remain the canonical source for current task instructions.

• Visit the Help Center