A Saved AI Answer Must Keep the Role It Was Written For
Changing Profile could not rewrite the framing of an old answer, so request context and stored response metadata followed separate frontend paths
Reviewed by Victor Sineglazov and Dmytro Nasyrov on October 22, 2026.
A reader changes their profession in Profile and reopens an answer saved earlier. If the answer header reads the current profile, it can claim that the old response was written for the new profession. The answer text has not changed; its description has become false.
Our frontend integration separated the current reader context from the context stored with an answer. The backend owned answer persistence and prompt construction. The interface had to carry the chosen context into new requests and render historical responses from their own saved metadata.
New requests and old answers use different sources
Send, edit, Try again and a follow-up from a saved answer carried profession through the request path. When no profession was selected, the argument was omitted. An absent choice did not become an invented default merely because the UI supported personalized states.
For display, the answer read its stored profession. This applied in the conversation and the saved-answer view. A later profile change could affect a new request without rewriting the apparent origin of an old answer.
| UI responsibility | Context source |
|---|---|
| Render an existing answer's scope | Profession stored with that answer |
| Start a new answer operation | The request's selected reader context |
| No profession selected | Omit the optional argument |
| Render a refusal | Do not attach the answer-only profession decorations |
The request matrix exposed missed paths
A successful initial send was insufficient. Editing and regeneration could use separate call sites, and a follow-up from Saved started on a different screen. We needed assertions for each path, otherwise one operation could silently stop carrying the context that the answer UI later described.
This is why a profile screenshot cannot verify personalization integration. It can show the selected label while the request omits it. A contract fixture and request assertion make the association inspectable before judging the model's response.
Refusals did not borrow answer-specific claims
For refusals, the role overline, scope block and footer were omitted. Reusing the complete answer shell would have made those decorations imply a personalized answer even where the system had declined to provide one. The stored profession also did not establish that the response was correct or appropriate. It recorded the requested framing. We keep that metadata claim distinct from model-quality evaluation and from the reader's real-world credentials.
A change-of-profile fixture is the useful artifact
Using a synthetic reader, the review sequence is concrete: obtain and save an answer under profession A, change Profile to B, then reopen the saved answer. Its historical scope should remain A. A later request may use B under the supported operation's rule. A refusal should omit the answer-specific framing. The letters here are scenario labels, not patient categories or clinical recommendations. They let a reviewer inspect whether the interface is reading the correct object without reproducing licensed source text.
The operation fixtures checked the argument, not the badge
New-question tests used two profiles: one with AESTHETICIAN and one with no profession. The first expected the optional profession argument; the second expected it to be absent. Separate request fixtures expected PRACTICE_OWNER for regeneration and STUDENT for editing. Those enum values are synthetic test inputs that expose the request paths. They do not measure whether any profession received a better answer.
In the saved-answer component, the two sources appear beside one another. Its answer presentation receives answer.profession. Its follow-up mutation uses the current reader's optional profession while keeping the saved answer's depth in that operation's request. The decisive fragments are:
// Historical answer presentation:
profession: answer.profession
// A follow-up uses the current reader's selected profession:
variables: {
chatId: chat.id,
content,
depth: answer.depth,
...(profession ? { profession } : {}),
}Each field has an owner and a lifetime. The follow-up belongs to the original conversation, borrows the supported depth context from the viewed answer and uses the present reader choice for profession.
The old answer's own scope remains historical.
A test can change only the metadata source and still find a defect
A useful display regression leaves the old answer text intact while supplying a profile with a different profession. The assertion then inspects the answer-specific overline and scope. If they change with the profile, the interface has relabeled history even though neither the stored response nor its requested framing changed.
For an unframed historical response, a missing stored profession should remain missing. Filling it from the current account would manufacture the same association in a less obvious way. Refusals retain their separate presentation rule rather than inheriting the complete-answer shell just because a request carried profession.
A fixture that gives the profile and the stored answer identical values cannot tell which object the renderer read. Deliberately separating them is what makes the source-of-truth error observable.
Evidence and ownership
The merged frontend work contains the request-path and saved-answer assertions, and its record reports local-cluster browser checks. These establish implementation behavior in that recorded environment, not a profession-specific model benchmark.
The distinction complements the separate case about versioned sources and frozen citations. Source provenance describes what material supported an answer; stored reader context describes the framing requested for that answer. Changing either current setting should not silently rewrite the other historical record.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 14
No matches
Try a different keyword, change the topic or clear filters
-
How long have you been in business?
Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).
-
What services do you provide?
Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).
-
Where is Pharos Production located?
Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.
-
How big is your team?
Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.
-
What types of customers do you serve?
We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.
-
How is a custom software development company different from an agency?
A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.
Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.
-
How much does custom software development cost?
Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).
-
How long does it take to develop a custom software application?
Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.
-
What industries does Pharos Production serve?
Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.
-
Why hire a software development company instead of building in-house?
Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.
Factor In-house team Software development company Time to assemble 3-6 months (recruiting + onboarding) 1-2 weeks Upfront cost High (salaries, benefits, equipment) Lower (project-based pricing) Specialized expertise Limited to who you can hire locally Access to 90+ engineers across blockchain, AI, FinTech Scalability Slow (each new hire takes months) Fast (scale up or down per sprint) Long-term commitment Full-time employment contracts Flexible engagement models Risk High if key engineers leave Company ensures continuity and knowledge transfer For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.
-
What projects does Pharos Production not take on?
Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.
-
Why does Pharos Production use agile methodology?
We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.
This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.
-
When should you NOT hire a custom software development company?
Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.
In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.
-
What kind of projects has Pharos Production delivered?
Here are three anonymized examples from our recent delivery history:
FinTech startup - payment platform (MVP)
Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.Healthcare provider - patient portal (Full product)
Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.Crypto exchange - trading engine (Complex)
Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.
Stas Rysin is the Lead Frontend Developer at Pharos Production. His work covers the design system, reader interfaces and administration workflows of a professional learning platform for aesthetic medicine.
